Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 03:29 UTC

paper-trail-gem / paper_trail

Track changes to your rails models

RubyMIT★ 7,032 stars⑂ 908 forkssince May 2009View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

paper-trail-gem/paper_trail holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Community & Adoption (90/100) and lowest on Vitality (30/100). It was last updated 111 days ago. A single contributor accounts for most of its recent work.

65
overall / 100
Good

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.

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

Ownership

10 followers4 public repossince May 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemspaper_trail17.0.0-122307 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
9.9/36Push recencylast push 111 days ago
2.8/36Commit cadence4/52 weeks with commits
8.1/18Commit volume7 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year7
human_commit_share1
days_since_last_push111
active_weeks_last_year4
How it's scored
27/27Ships releases36 releases published
0/36Release recencylatest release 1,662 days ago
12.6/27Release cadencea release every ~210.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count36
latest_release_tag999.9.9
releases_from_tagsno
days_since_latest_release1,662
mean_days_between_releases210.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?

90Excellent · 17% of overall
How it's scored
60/60Stars7,032 stars
24.7/25Forks908 forks
9.8/15Watchers60 watchers
Inputs used
forks908
stars7,032
watchers60
growth_stateorganic
growth_factor_pct100
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
80/80Total downloads145,546,148 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagespaper_trail
dependents
ecosystemsrubygems
total_downloads145,546,148
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
10.5/22.5Commit distributiontop contributor authored 54% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 43 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled100
top_contributor_share0.535
How it's scored
41.8/42Issue resolution100% of issues closed
21.8/30PR acceptance571/784 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
7.5/15OpenSSF Scorecard: Code-ReviewFound 14/28 approved changesets -- score normalized to 5
Inputs used
merged_prs571
open_issues4
closed_issues753
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0.995
closed_unmerged_prs213
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
7.5/25Owner reach10 followers of paper-trail-gem
17.1/25Track record4 public repos, account ~8 yr old
Inputs used
followers10
owner_typeOrganization
is_verifiedno
owner_loginpaper-trail-gem
public_repos4
account_age_days3,037
How it's scored
25/25Published & resolvable1 package(s) on rubygems
26/35Publish recencylatest publish 307 days ago
20/20Version history122 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespaper_trail
ecosystemsrubygems
any_deprecatedno
min_days_since_publish307

Engineering Quality

Are baseline engineering and documentation practices in place?

75Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests6 out of 21 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsruby, activerecord, audit, log, rails
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

49Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.5/2.5CI-Tests6 out of 21 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-ReviewFound 14/28 approved changesets -- score normalized to 5
2.5/2.5Contributorsproject has 43 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

35Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
27.7/40Legible commit history52 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.52
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
0/8Automated maintenanceno automated dependency updates observed
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
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/204 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes34,381
source_files_sampled204
oversized_source_files0

Key facts

7,032GitHub stars
100contributors
7commits, last 12 months
111days since last push
36releases
1bus factor
4open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-16: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 7032 stars today.
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 7,025 ★ / 908 ⇿
7,025Stars
908Forks
36Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-07-16. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

01,2502,5003,7505,0006,2507,5007,025884232009-112018-032026-08
Major 6Minor 4Patch 19

Each point covers 16 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-28 03:28 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
2CI-Tests6 out of 21 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 14/28 approved changesets -- score normalized to 5
10Contributorsproject has 43 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
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
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
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 24

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

RegistryPackageVersionRelation
RubyGemsappraisalindirect
RubyGemsbenchmarkindirect
RubyGemsbigdecimalindirect
RubyGemsbyebugindirect
RubyGemsdrbindirect
RubyGemsffakerindirect
RubyGemsgenerator_specindirect
RubyGemsloggerindirect
RubyGemsmemory_profilerindirect
RubyGemsmutex_mindirect
RubyGemsmysql2indirect
RubyGemspgindirect
RubyGemsrails-controller-testingindirect
RubyGemsrakeindirect
RubyGemsrequest_storeindirect
RubyGemsrspec-railsindirect
RubyGemsrubocopindirect
RubyGemsrubocop-packagingindirect
RubyGemsrubocop-performanceindirect
RubyGemsrubocop-railsindirect
RubyGemsrubocop-rakeindirect
RubyGemsrubocop-rspecindirect
RubyGemssimplecovindirect
RubyGemssqlite3indirect
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.