Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 15:24 UTC

voxpupuli / facterdb

A Database of OS facts provided by Facter

Ruby · Shell · PowerShellApache-2.0★ 43 stars⑂ 82 forkssince May 2015View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

voxpupuli/facterdb holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (86/100) and lowest on AI Readiness (37/100). It was last updated today. A single contributor accounts 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

Vox PupuliOrganization
206 followers391 public repossince Sep 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsfacterdb4.5.0-790 days ago

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
13.8/36Commit cadence20/52 weeks with commits
18/18Commit volume122 commits in the last year
7/10OpenSSF Scorecard: Maintained8 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year122
human_commit_share0.85
days_since_last_push0
active_weeks_last_year20
How it's scored
27/27Ships releases9 releases published
36/36Release recencylatest release 0 days ago
19.8/27Release cadencea release every ~53.4 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count9
latest_release_tag4.5.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases53.4

Community & Adoption

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

73Good · 17% of overall
How it's scored
26.3/60Stars43 stars
15.9/25Forks82 forks
8.8/15Watchers39 watchers
Inputs used
forks82
stars43
watchers39
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
72.5/80Total downloads9,567,677 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesfacterdb
dependents
ecosystemsrubygems
total_downloads9,567,677
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?

77Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.7/22.5Commit distributiontop contributor authored 53% of commits
13.5/13.5Contributor breadth63 contributors
10/10OpenSSF Scorecard: Contributorsproject has 51 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled63
top_contributor_share0.526
How it's scored
36.8/42Issue resolution88% of issues closed
26.7/30PR acceptance344/386 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 3/5 approved changesets -- score normalized to 6
Inputs used
merged_prs344
open_issues9
closed_issues63
prs_merged_7d1
prs_decided_7d1
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.875
closed_unmerged_prs42
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
16.7/25Owner reach206 followers of voxpupuli
25/25Track record391 public repos, account ~11 yr old
Inputs used
followers206
owner_typeOrganization
is_verified
owner_loginvoxpupuli
public_repos391
account_age_days4,357
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 history79 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesfacterdb
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 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
20/20OpenSSF Scorecard: CI-Tests6 out of 6 merged PRs checked by a CI test -- score normalized to 10
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 sitehttp://voxpupuli.org/facterdb/
10/10Repository description
10/10Topics2 topics
0/10Wiki
Inputs used
topicshacktoberfest, ruby
has_wikino
homepagehttp://voxpupuli.org/facterdb/
docs_sitehttp://voxpupuli.org/facterdb/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

73Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests6 out of 6 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 3/5 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 51 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
5.2/7.5Maintained8 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 7
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
4/5SASTSAST tool is not run on all commits -- score normalized to 8
4.5/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.3
Excluded from scoring (no data or not applicable): Branch-Protection. 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.

37Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
22.6/40Legible commit history36 of 85 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.424
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 maintenance15 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.15
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/17 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes8,381
source_files_sampled17
oversized_source_files0

Key facts

43GitHub stars
63contributors
122commits, last 12 months
0days since last push
9releases
1bus factor
9open 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 ★ / 82 ⇿
0Stars
82Forks
8Releases

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.

0204060801008222015-082021-022026-08
Major 1Minor 7Patch 0

Each point covers 10 days.

OpenSSF Scorecard 7.3 / 10
7.3aggregate

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-13 15:23 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
10CI-Tests6 out of 6 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 3/5 approved changesets -- score normalized to 6
10Contributorsproject has 51 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
7Maintained8 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 7
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
8SASTSAST tool is not run on all commits -- score normalized to 8
9Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
RubyGemsfaraday-retry~> 2.1Gemfile
RubyGemsgithub_changelog_generator~> 1.18Gemfile
RubyGemsyard~> 0.9.43Gemfile
RubyGemsffifacts/Gemfile
RubyGemsjsonfacts/Gemfile
RubyGemssys-filesystemfacts/Gemfile
RubyGemsfacterfacts/Gemfile
All dependencies 11

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

RegistryPackageVersionRelation
RubyGemsfaraday-retrydirect
RubyGemsffidirect
RubyGemsgithub_changelog_generatordirect
RubyGemsjsondirect
RubyGemssys-filesystemdirect
RubyGemsyarddirect
RubyGemscoverallsindirect
RubyGemsjgrepindirect
RubyGemsrakeindirect
RubyGemsrspecindirect
RubyGemsvoxpupuli-rubocopindirect
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.31.0 — full methodology · metrics wiki.

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