Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 06:24 UTC

DataDog / datadog-ci-rb

Ruby library for Datadog Test Optimization

RubyCustom license★ 28 stars⑂ 13 forkssince Mar 2023View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

DataDog/datadog-ci-rb holds a health index of 94 out of 100, placing it in the Exceptional band. It scores highest on Vitality (98/100) and lowest on AI Readiness (68/100). It was last updated today. A single contributor accounts for most of its recent work.

94
overall / 100
Exceptional

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.

94
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 81 is calibrated to 94 on the published index scale (record calibration 2026-08-02).

Ownership

Datadog, Inc.Organization · verified domain
3,303 followers1,203 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-ci1.38.1-715 days ago

Metrics by category

Vitality

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

98Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
32.5/36Commit cadence — 47/52 weeks with commits
18/18Commit volume — 616 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year616
human_commit_share0.81
days_since_last_push0
active_weeks_last_year47

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 70 releases published
36/36Release recency — latest release 5 days ago
27/27Release cadence — a release every ~12.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count70
latest_release_tagv1.38.1
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases12.2
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?

68Good · 17% of overall
How it's scored
23.2/60Stars — 28 stars
9/25Forks — 13 forks
1.7/15Watchers — 3 watchers
Inputs used
forks13
stars28
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, shields.io
has_pull_request_templateyes
How it's scored
78.4/80Total downloads — 34,745,220 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesdatadog-ci
dependents—
ecosystemsrubygems
total_downloads34,745,220
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?

79Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.6/22.5Commit distribution — top contributor authored 97% of commits
13.5/13.5Contributor breadth — 10 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled10
top_contributor_share0.972
How it's scored
42/42Issue resolution — 100% of issues closed
28/30PR acceptance — 533/571 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs533
open_issues0
closed_issues42
prs_merged_7d6
prs_decided_7d6
prs_merged_30d16
prs_decided_30d17
issue_closed_ratio1
closed_unmerged_prs38
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 3,303 followers of DataDog
25/25Track record — 1,203 public repos, account ~16 yr old
Inputs used
followers3,303
owner_typeOrganization
is_verifiedyes
owner_loginDataDog
public_repos1,203
account_age_days5,872

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
35/35Publish recency — latest publish 5 days ago
20/20Version history — 71 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesdatadog-ci
ecosystemsrubygems
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

85Excellent · 19% of overall
How it's scored
24/24CI workflows — 11 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 9 out of 10 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://docs.datadoghq.com/tests/setup/ruby/?tab=cloudciprovideragentless
10/10Repository description
10/10Topics — 8 topics
0/10Wiki
Inputs used
topicsci, observability, ruby, datadog, selective-testing, test-impact-analysis, testing, testing-tools
has_wikino
homepagehttps://docs.datadoghq.com/tests/setup/ruby/?tab=cloudciprovideragentless
docs_sitehttps://docs.datadoghq.com/tests/setup/ruby/?tab=cloudciprovideragentless
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

72Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.2/2.5CI-Tests — 9 out of 10 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 4 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
4.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
3.5/5SAST — SAST tool detected but not run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.2
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

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.

68Good · 4% of overall
How it's scored
45/45Agent instructions — .cursor/rules/architecture.mdc, .cursor/rules/code-style.mdc, .cursor/rules/testing.mdc, AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.datadoghq.com/llms.txt)
24.4/40Legible commit history — 37 of 81 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.datadoghq.com/llms.txt
legible_history_share0.457
agent_instruction_files.cursor/rules/architecture.mdc, .cursor/rules/code-style.mdc, .cursor/rules/testing.mdc, AGENTS.md, CLAUDE.md
agent_instruction_max_bytes3,367
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 1 of the last 100 commits are automated dependency updates
9/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.01
How it's scored
0/45Type-checkable code — Ruby without a type-check config
54.8/55Manageable file sizes — 2/505 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes120,240
source_files_sampled505
oversized_source_files2

Key facts

28GitHub stars
10contributors
616commits, last 12 months
0days since last push
70releases
1bus factor
0open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 13 ⇿
0Stars
13Forks
68Releases

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.

03581013151312023-092025-032026-08
Major 1Minor 45Patch 16

Each point covers 3 days.

OpenSSF Scorecard 7.2 / 10
7.2aggregate

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-09-13 06:24 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests9 out of 10 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow 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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 23
RegistryPackageVersion constraintManifest
RubyGemsdebug—Gemfile
RubyGemsrake-compiler—Gemfile
RubyGemssimplecov—Gemfile
RubyGemsrspec—Gemfile
RubyGemsrspec-collection_matchers—Gemfile
RubyGemsrspec_junit_formatter—Gemfile
RubyGemsappraisal—Gemfile
RubyGemsclimate_control—Gemfile
RubyGemswebmock—Gemfile
RubyGemsrake—Gemfile
RubyGemsyard—Gemfile
RubyGemsostruct—Gemfile
RubyGemsdatadog—Gemfile
RubyGemsos—Gemfile
RubyGemsstandard~> 1.56Gemfile
RubyGemsarchspec~> 1.1.0Gemfile
RubyGemsrbs~> 4.2Gemfile
RubyGemssteep~> 2.1Gemfile
RubyGemsruby_memcheck>= 3Gemfile
RubyGemsredcarpet—Gemfile
RubyGemswebrick—Gemfile
RubyGemspimpmychangelog>= 0.1.2Gemfile
RubyGemsirb—Gemfile
All dependencies 24

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

RegistryPackageVersionRelation
RubyGemsappraisal—direct
RubyGemsclimate_control—direct
RubyGemsdatadog—direct
RubyGemsos—direct
RubyGemsostruct—direct
RubyGemspimpmychangelog—direct
RubyGemsrake—direct
RubyGemsrake-compiler—direct
RubyGemsrbs—direct
RubyGemsrspec—direct
RubyGemsrspec-collection_matchers—direct
RubyGemsrspec_junit_formatter—direct
RubyGemssimplecov—direct
RubyGemssteep—direct
RubyGemswebmock—direct
RubyGemswebrick—direct
RubyGemsyard—direct
RubyGemscucumber—indirect
RubyGemsdatadog-ci—indirect
RubyGemsdrb—indirect
RubyGemsmsgpack—indirect
RubyGemspry—indirect
RubyGemsruby-lsp—indirect
RubyGemsruby-lsp-rspec—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — RubyGems.