Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 13:44 UTC

dnsimple / dnsimple-ruby

The DNSimple API client for Ruby.

RubyMIT★ 189 stars⑂ 51 forkssince Jul 2010View on GitHub ↗

dnsimple/dnsimple-ruby holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (82/100) and lowest on AI Readiness (46/100). It was last updated today. 2 contributors account for most of its recent work.

86
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.

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

Ownership

DNSimpleOrganization · verified domain
79 followers39 public repossince May 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsdnsimple13.1.0-480 days ago

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
15.9/36Commit cadence23/52 weeks with commits
16.5/18Commit volume68 commits in the last year
10/10OpenSSF Scorecard: Maintained15 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year68
human_commit_share0.6
days_since_last_push0
active_weeks_last_year23
How it's scored
16.2/27Ships releases63 version tags (no GitHub releases)
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~43.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count63
latest_release_tagv13.1.0
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases43.7
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
36.9/60Stars189 stars
14.2/25Forks51 forks
4.7/15Watchers8 watchers
Inputs used
forks51
stars189
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
68.2/80Total downloads3,676,391 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesdnsimple
dependents
ecosystemsrubygems
total_downloads3,676,391
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?

80Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.8/22.5Commit distributiontop contributor authored 43% of commits
13.5/13.5Contributor breadth36 contributors
10/10OpenSSF Scorecard: Contributorsproject has 20 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled36
top_contributor_share0.429
How it's scored
42/42Issue resolution100% of issues closed
23.7/30PR acceptance336/426 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 2/15 approved changesets -- score normalized to 1
Inputs used
merged_prs336
open_issues0
closed_issues58
prs_merged_7d2
prs_decided_7d2
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio1
closed_unmerged_prs90
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
13.7/25Owner reach79 followers of dnsimple
23.7/25Track record39 public repos, account ~14 yr old
Inputs used
followers79
owner_typeOrganization
is_verifiedyes
owner_logindnsimple
public_repos39
account_age_days5,232

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

75Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests19 out of 20 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
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://developer.dnsimple.com/
10/10Repository description
10/10Topics8 topics
0/10Wiki
Inputs used
topicsruby, dnsimple-api, dnsimple, api, api-client, dnsimple-policy-group-apiclient, dnsimple-policy-eng, dnsimple-policy-triage-application
has_wikino
homepagehttps://developer.dnsimple.com/
docs_sitehttps://developer.dnsimple.com/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

52Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.2/2.5CI-Tests19 out of 20 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 2/15 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 20 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.5Maintained15 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.2
Excluded from scoring (no data or not applicable): Packaging, 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://developer.dnsimple.com/llms.txt)
32.9/40Legible commit history37 of 60 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://developer.dnsimple.com/llms.txt
legible_history_share0.617
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance28 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.28
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/117 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes26,936
source_files_sampled117
oversized_source_files0

Key facts

189GitHub stars
36contributors
68commits, last 12 months
0days since last push
63releases
2bus 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 ★ / 51 ⇿
0Stars
51Forks
50Releases

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.

010203040504922011-102018-042024-10
Major 9Minor 27Patch 13

Each point covers 12 days.

OpenSSF Scorecard 5.2 / 10
5.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-18 13:43 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
9CI-Tests19 out of 20 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/15 approved changesets -- score normalized to 1
10Contributorsproject has 20 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained15 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
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 8
RegistryPackageVersion constraintManifest
RubyGemsbase64~> 0.3.0Gemfile
RubyGemsbigdecimal~> 4.0Gemfile
RubyGemscoveralls~> 0.8Gemfile
RubyGemscsv~> 3.2Gemfile
RubyGemsrubocop~> 1.75Gemfile
RubyGemsrubocop-minitest~> 0.36Gemfile
RubyGemsrubocop-performance~> 1.25Gemfile
RubyGemsrubocop-rake~> 0.7Gemfile
All dependencies 14

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

RegistryPackageVersionRelation
RubyGemsbase64direct
RubyGemsbigdecimaldirect
RubyGemscoverallsdirect
RubyGemscsvdirect
RubyGemsrubocopdirect
RubyGemsrubocop-minitestdirect
RubyGemsrubocop-performancedirect
RubyGemsrubocop-rakedirect
RubyGemshttpartyindirect
RubyGemsminitestindirect
RubyGemsminitest-mockindirect
RubyGemsrakeindirect
RubyGemswebmockindirect
RubyGemsyardindirect
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 statisticsRubyGems.