Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-07 08:25 UTC

DataDog / datadog-api-client-ruby

Ruby client for the Datadog API

RubyApache-2.0★ 44 stars⑂ 20 forkssince Jul 2020View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

DataDog/datadog-api-client-ruby holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Vitality (99/100) and lowest on AI Readiness (46/100). It was last updated today. 4 contributors account for most of its recent work.

90
overall / 100
Excellent

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

90
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 76 is calibrated to 90 on the published index scale (record calibration 2026-08-02).

Ownership

Datadog, Inc.Organization
3,251 followers1,198 public repossince Aug 2010

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsdatadog_api_client2.57.0-760 days ago
PyPIgeneratorpoints to another repo — not scored0.1-alpha1015224 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

99Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
35.3/36Commit cadence51/52 weeks with commits
18/18Commit volume770 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year770
human_commit_share0.03
days_since_last_push0
active_weeks_last_year51

Release discipline

100Exceptional
How it's scored
27/27Ships releases77 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~23.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count77
latest_release_tagv2.57.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases23.4
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

64Moderate · 17% of overall
How it's scored
26.5/60Stars44 stars
10.7/25Forks20 forks
15/15Watchers494 watchers
Inputs used
forks20
stars44
watchers494
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
75.6/80Total downloads18,701,109 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesdatadog_api_client
dependents
ecosystemsrubygems
total_downloads18,701,109
monthly_downloads
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

88Excellent · 23% of overall
How it's scored
43.2/54Bus factor4 contributor(s) cover half of all commits
17.9/22.5Commit distributiontop contributor authored 20% of commits
13.5/13.5Contributor breadth62 contributors
10/10OpenSSF Scorecard: Contributorsproject has 13 contributing companies or organizations
Inputs used
bus_factor4
contributors_sampled62
top_contributor_share0.203
How it's scored
35.4/42Issue resolution84% of issues closed
24.2/30PR acceptance2,873/3,566 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs2,873
open_issues3
closed_issues16
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0.842
closed_unmerged_prs693
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Code-Review. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach3,251 followers of DataDog
25/25Track record1,198 public repos, account ~15 yr old
Inputs used
followers3,251
owner_typeOrganization
is_verified
owner_loginDataDog
public_repos1,198
account_age_days5,835
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 0 days ago
20/20Version history76 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesdatadog_api_client
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows14 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests1 out of 30 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://www.rubydoc.info/gems/datadog_api_client
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsdatadog, datadog-api, openapi, ruby
has_wikino
homepagehttps://www.rubydoc.info/gems/datadog_api_client
docs_sitehttps://www.rubydoc.info/gems/datadog_api_client
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

57Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Tests1 out of 30 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-Reviewno data
2.5/2.5Contributorsproject has 13 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
4.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
3.5/5SASTSAST tool detected but not run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
2.2/7.5Vulnerabilities7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6
Excluded from scoring (no data or not applicable): Code-Review, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
7.7/35Direct dependencies free of known advisories3 affected: click 8.1.7 (high 7.2), jinja2 3.1.4 (high 8.8), pytest 7.4.4 (moderate 6.8)
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
25.5/40No advisories left outstanding3 advisory-carrying package(s) unaddressed past 90 days; oldest published 591 days ago
Inputs used
sourceosv
advisories13
affected_packages4
assessed_packages21
unassessed_packages22
affected_by_severityhigh 3, moderate 1
direct_affected_packages3
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 21 resolved dependencies against OSV. 22 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

46Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
10/10Reproducible environmentlockfile
4/10Demonstrated agent practice2 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
9/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.02
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeRuby without a type-check config
54.9/55Manageable file sizes24/10,843 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes722,886
source_files_sampled10,843
oversized_source_files24
How it's scored
40/40API schema (OpenAPI/GraphQL/proto).generator/schemas/v1/openapi.yaml, .generator/schemas/v2/openapi.yaml
20/20MCP server
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files.generator/schemas/v1/openapi.yaml, .generator/schemas/v2/openapi.yaml
interfaces_expected_of

Key facts

44GitHub stars
62contributors
770commits, last 12 months
0days since last push
77releases
4bus factor
3open issues
PyPI, RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi package 'generator' points at a different repository (UNKNOWN); excluded from ecosystem scoring
  • deps.dev does not index pypi:generator@0.1-alpha; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 20 ⇿
0Stars
20Forks
49Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

0481216202012021-012023-032025-04
Major 2Minor 39Patch 7

Each point covers 4 days.

OpenSSF Scorecard 6.0 / 10
6.0aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-07 08:24 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests1 out of 30 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
n/aCode-ReviewFound no human activity in the last 30 changesets
10Contributorsproject has 13 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
9Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
7SASTSAST tool detected but not run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
3Vulnerabilities7 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
PyPIclick^8.1.4.generator/pyproject.toml
PyPIpyyaml^6.0.generator/pyproject.toml
PyPIjsonref^1.1.0.generator/pyproject.toml
PyPIjinja2^3.1.2.generator/pyproject.toml
PyPIpytest^7.4.0.generator/pyproject.toml
PyPIpytest-bdd^6.1.1.generator/pyproject.toml
PyPIpython-dateutil^2.8.2.generator/pyproject.toml
RubyGemsgithub-markupGemfile
RubyGemsredcarpetGemfile
RubyGemsyardGemfile
All dependencies 43

Full resolved dependency set from the GitHub dependency graph: 10 direct and 33 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
PyPIclick8.1.7direct
PyPIjinja23.1.4direct
PyPIjsonref1.1.0direct
PyPIpytest7.4.4direct
PyPIpytest-bdd6.1.1direct
PyPIpython-dateutil2.9.0.post0direct
PyPIpyyaml6.0.2direct
RubyGemsgithub-markupdirect
RubyGemsredcarpetdirect
RubyGemsyarddirect
PyPIcolorama0.4.6indirect
PyPIexceptiongroup1.2.2indirect
PyPIiniconfig2.0.0indirect
PyPImako1.3.6indirect
PyPImarkupsafe3.0.2indirect
PyPIpackaging24.2indirect
PyPIparse1.20.2indirect
PyPIparse-type0.6.4indirect
PyPIpluggy1.5.0indirect
PyPIsix1.16.0indirect
PyPItomli2.1.0indirect
PyPItyping-extensions4.12.2indirect
RubyGemsactivesupportindirect
RubyGemsbigdecimal3.1.9indirect
RubyGemscucumberindirect
RubyGemsdatadog-ciindirect
RubyGemsgem-releaseindirect
RubyGemshttpartyindirect
RubyGemsi18nindirect
RubyGemslibddwaf1.18.0.0.1indirect
RubyGemsostructindirect
RubyGemspryindirect
RubyGemsrakeindirect
RubyGemsrspecindirect
RubyGemsrspec-expectationsindirect
RubyGemsrubocopindirect
RubyGemsrufoindirect
RubyGemssimplecovindirect
RubyGemstimecopindirect
RubyGemsvcrindirect
RubyGemswebmockindirect
RubyGemszeitwerkindirect
RubyGemszstandardindirect
Dependency advisories 4

This repository publishes no package the index resolves, so its own dependency graph was assessed — 21 packages, which also include development and test pins that never ship: 4 carry known advisories, of which 3 are direct. 22 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
click8.1.7directhigh18.3.3
jinja23.1.4directhigh63.1.6
mako1.3.6indirecthigh41.3.12
pytest7.4.4directmoderate29.0.3

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsRubyGems, PyPI.