Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 12:19 UTC

westonganger / active_snapshot

Simplified snapshots and restoration for ActiveRecord models and associations with a transparent white-box implementation

RubyMIT★ 191 stars⑂ 26 forkssince Sep 2020View on GitHub ↗
KindLibraryPluginNetwork servicehow this is determined

westonganger/active_snapshot holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Vitality (77/100) and lowest on AI Readiness (28/100). It was last updated 1 day 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

Weston GangerPersonal account
106 followers137 public repossince Jan 2013Braintree / Paypal

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsactive_snapshot1.2.2-191 day ago

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
8.3/36Commit cadence12/52 weeks with commits
12.4/18Commit volume23 commits in the last year
10/10OpenSSF Scorecard: Maintained13 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year23
human_commit_share1
days_since_last_push1
active_weeks_last_year12
How it's scored
27/27Ships releases18 releases published
36/36Release recencylatest release 50 days ago
19.8/27Release cadencea release every ~112.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count18
latest_release_tagv1.2.1
releases_from_tagsno
days_since_latest_release50
mean_days_between_releases112.3
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?

56Moderate · 17% of overall
How it's scored
37/60Stars191 stars
11.7/25Forks26 forks
0/15Watchers1 watchers
Inputs used
forks26
stars191
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, github.com, shields.io
has_pull_request_templateno
How it's scored
61/80Total downloads734,893 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesactive_snapshot
dependents
ecosystemsrubygems
total_downloads734,893
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.4/22.5Commit distributiontop contributor authored 85% of commits
13.5/13.5Contributor breadth15 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled15
top_contributor_share0.848
How it's scored
38.3/42Issue resolution91% of issues closed
25.4/30PR acceptance44/52 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 8/30 approved changesets -- score normalized to 2
Inputs used
merged_prs44
open_issues3
closed_issues31
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.912
closed_unmerged_prs8
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
14.6/25Owner reach106 followers of westonganger
25/25Track record137 public repos, account ~13 yr old
Inputs used
followers106
owner_typeUser
is_verified
owner_loginwestonganger
public_repos137
account_age_days4,975
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 1 days ago
20/20Version history19 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesactive_snapshot
ecosystemsrubygems
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

62Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests12 out of 14 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics9 topics
10/10Wiki
Inputs used
topicsrails, versioning, model-snapshots, model-versioning, activerecord, audit, associations, restore-data, ruby
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

42Weak · 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.5CI-Tests12 out of 14 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 8/30 approved changesets -- score normalized to 2
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
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
7.5/7.5Maintained13 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_aggregate4.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.

28At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
19.7/40Legible commit history37 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.37
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
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_configno
typecheck_configs
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/50 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes17,048
source_files_sampled50
oversized_source_files0

Key facts

191GitHub stars
15contributors
23commits, last 12 months
1days since last push
18releases
1bus factor
3open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 26 ⇿
0Stars
26Forks
16Releases

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.

0510152025302622021-042023-122026-08
Major 1Minor 6Patch 9

Each point covers 5 days.

OpenSSF Scorecard 4.2 / 10
4.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 12:18 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests12 out of 14 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 8/30 approved changesets -- score normalized to 2
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained13 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 1
RegistryPackageVersion constraintManifest
RubyGemsrailsGemfile
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.