Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 00:15 UTC

mocktools / ruby-dns-mock

DNS mock server written on 💎 Ruby. Mimic any DNS records for your test environment with fake DNS server.

RubyMIT★ 66 stars⑂ 7 forkssince Dec 2020View on GitHub ↗

mocktools/ruby-dns-mock holds a health index of 37 out of 100, placing it in the Weak band. It scores highest on Community & Adoption (63/100) and lowest on Vitality (30/100). It was last updated 339 days ago. A single contributor accounts for most of its recent work.

37
overall / 100
Weak

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.

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

Ownership

mocktoolsOrganization
5 followers4 public repossince Dec 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsdns_mock1.7.6-46625 days ago

Metrics by category

Vitality

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

30At Risk · 21% of overall
How it's scored
3.6/36Push recency — last push 339 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push339
active_weeks_last_year0
How it's scored
27/27Ships releases — 46 releases published
7.2/36Release recency — latest release 625 days ago
27/27Release cadence — a release every ~39.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count46
latest_release_tagv1.7.6
releases_from_tagsno
days_since_latest_release625
mean_days_between_releases39.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?

63Moderate · 17% of overall
How it's scored
29.4/60Stars — 66 stars
6.5/25Forks — 7 forks
0/15Watchers — 1 watchers
Inputs used
forks7
stars66
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
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_badges7
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesapi.codeclimate.com, badge.fury.io, circleci.com, shields.io
has_pull_request_templateyes
How it's scored
53.5/80Total downloads — 139,818 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesdns_mock
dependents—
ecosystemsrubygems
total_downloads139,818
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?

55Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution — 100% of issues closed
29.6/30PR acceptance — 151/153 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs151
open_issues0
closed_issues6
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs2
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 backing — organization-owned
0/20Verified domain
5.6/25Owner reach — 5 followers of mocktools
16.5/25Track record — 4 public repos, account ~5 yr old
Inputs used
followers5
owner_typeOrganization
is_verifiedno
owner_loginmocktools
public_repos4
account_age_days2,091
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
14/35Publish recency — latest publish 625 days ago
20/20Version history — 46 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesdns_mock
ecosystemsrubygems
any_deprecatedno
min_days_since_publish625

Engineering Quality

Are baseline engineering and documentation practices in place?

50Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 30 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://github.com/mocktools/ruby-dns-mock/blob/master/README.md
10/10Repository description
10/10Topics — 14 topics
0/10Wiki
Inputs used
topicsdns, mock, dns-mock, mock-server, mocktools, ruby, rspec, hacktoberfest, dns-server, fake-server, fake-dns, testing, testing-tools, developer-tools
has_wikino
homepage—
docs_sitehttps://github.com/mocktools/ruby-dns-mock/blob/master/README.md
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

32At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 30 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 6 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.2
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

41Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 99 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.99
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 practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
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
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/102 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes10,869
source_files_sampled102
oversized_source_files0

Key facts

66GitHub stars
1contributors
0commits, last 12 months
339days since last push
46releases
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 ★ / 7 ⇿
0Stars
7Forks
27Releases

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.

1234567722022-022024-052026-08
Major 0Minor 2Patch 25

Each point covers 5 days.

OpenSSF Scorecard 3.2 / 10
3.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-12 00:15 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
0CI-Tests0 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
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 4

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

RegistryPackageVersionRelation
RubyGemsrake—indirect
RubyGemsrspec—indirect
RubyGemsrspec-dns—indirect
RubyGemssimpleidn—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.