Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 14:38 UTC

disintegrator / bumper

Manage versioning and changelogs at scale with ease

Go · MDXMPL-2.0★ 1 star⑂ 0 forkssince Nov 2025View on GitHub ↗
KindApplicationLibraryhow this is determined

disintegrator/bumper holds a health index of 53 out of 100, placing it in the Moderate band. It scores highest on AI Readiness (83/100) and lowest on Community & Adoption (12/100). It was last updated 12 days ago. A single contributor accounts for most of its recent work.

53
overall / 100
Moderate

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.

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

Ownership

Georges HaidarPersonal account
84 followers110 public repossince Mar 2011GoCardless

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 publishTags
Gogithub.com/disintegrator/bumperv0.1.0-853 days ago
npmsite2.60.43,2472371344 days agogameappwebsiteframeworkengineanimationhtml5svghtmlwebblog

Metrics by category

Vitality

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

76Good · 21% of overall
How it's scored
28.8/36Push recencylast push 12 days ago
4.2/36Commit cadence6/52 weeks with commits
18/18Commit volume115 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year115
human_commit_share0.58
days_since_last_push12
active_weeks_last_year6

Release discipline

98Exceptional
How it's scored
27/27Ships releases8 releases published
36/36Release recencylatest release 53 days ago
27/27Release cadencea release every ~37.4 days
8/10OpenSSF Scorecard: Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count8
latest_release_tagv0.1.0
releases_from_tagsno
days_since_latest_release53
mean_days_between_releases37.4

Community & Adoption

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

12Critical · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5Licenserecognized license (MPL-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

54Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
29.1/42Issue resolution69% of issues closed
22.5/30PR acceptance57/76 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/18 approved changesets -- score normalized to 0
Inputs used
merged_prs57
open_issues4
closed_issues9
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.692
closed_unmerged_prs19
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
13.9/25Owner reach84 followers of disintegrator
25/25Track record110 public repos, account ~15 yr old
Inputs used
followers84
owner_typeUser
is_verified
owner_logindisintegrator
public_repos110
account_age_days5,663
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on go, npm
35/35Publish recencylatest publish 53 days ago
20/20Version history237 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/disintegrator/bumper, site
ecosystemsgo, npm
any_deprecatedno
min_days_since_publish53

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

60Moderate
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage sitehttp://bumper.disintegrator.dev/
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicschangelog, changesets, release-automation, semantic-versioning, semver
has_wikino
homepagehttp://bumper.disintegrator.dev/
docs_sitehttp://bumper.disintegrator.dev/
has_readmeno
has_docs_diryes
has_descriptionyes

Security

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

53Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Tests0 out of 24 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/18 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
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.5Maintained30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
5/5Pinned-Dependenciesall dependencies are pinned
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
6/7.5Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
6.8/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities41 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate5.9
How it's scored
14/35Direct dependencies free of known advisories1 affected: terser 3.17.0 (high 7.5)
1.8/25Indirect dependencies free of known advisories13 affected: babel-traverse 6.26.0 (critical 9.3), xmldom 0.1.19 (critical 9.8), braces 1.8.5 (high 7.5), +10 more
12.1/40No advisories left outstanding13 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,016 days ago
Inputs used
sourceosv
advisories31
affected_packages14
assessed_packages270
unassessed_packages0
affected_by_severitycritical 2, high 7, moderate 5
direct_affected_packages1
Matched the npm:site@2.60.4 runtime dependency closure — what installing the published package pulls in — 270 packages. Reachability is not analyzed.

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.

83Excellent · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
21.1/40Legible commit history23 of 58 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.397
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes4,102
How it's scored
18/18One-command bootstrapmise.toml
22/22Automated tests
0/11Lint / format config
11/11Static type checkingsite/tsconfig.json, tsconfig.json
10/10Reproducible environmentlockfile
10/10Demonstrated agent practice17 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance37 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesmise.toml
has_devcontainerno
has_linter_configno
typecheck_configssite/tsconfig.json, tsconfig.json
agent_commit_share0.17
toolchain_manifestsgo.mod
dependency_bot_commit_share0.37
How it's scored
45/45Type-checkable codeGo (statically typed)
55/55Manageable file sizes0/44 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes8,581
source_files_sampled44
oversized_source_files0

Key facts

1GitHub stars
1contributors
115commits, last 12 months
12days since last push
8releases
1bus factor
4open issues
Go, npmpackage 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

OpenSSF Scorecard 5.9 / 10
5.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-09-19 14:38 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 24 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/18 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities41 existing vulnerabilities detected
Direct dependencies 17
RegistryPackageVersion constraintManifest
Gogithub.com/BurntSushi/tomlv1.6.0go.mod
Gogithub.com/Masterminds/semver/v3v3.5.0go.mod
Gogithub.com/charmbracelet/huhv1.0.0go.mod
Gogithub.com/charmbracelet/logv1.0.0go.mod
Gogithub.com/creachadair/tomleditv0.0.29go.mod
Gogithub.com/go-git/go-git/v6v6.0.0-alpha.4go.mod
Gogithub.com/goccy/go-yamlv1.19.2go.mod
Gogithub.com/samber/lov1.53.0go.mod
Gogithub.com/tidwall/gjsonv1.14.2go.mod
Gogithub.com/tidwall/sjsonv1.2.5go.mod
Gogithub.com/urfave/cli/v3v3.10.1go.mod
npm@astrojs/starlight^0.41.4site/package.json
npm@astrojs/starlight-tailwind^5.0.0site/package.json
npm@tailwindcss/vite^4.3.3site/package.json
npmastro^7.1.3site/package.json
npmsharp^0.35.3site/package.json
npmtailwindcss^4.3.3site/package.json
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

Dependency advisories 14

Installing npm:site@2.60.4 pulls in 270 packages, direct and transitive: 14 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
babel-traverse6.26.0indirectcritical18.0.0-alpha.4
xmldom0.1.19indirectcritical160.9.12
terser3.17.0directhigh15.14.2
braces1.8.5indirecthigh13.0.3
braces2.3.2indirecthigh13.0.3
decode-uri-component0.2.2indirecthigh10.5.0
form-data2.3.3indirecthigh24.0.6
json50.5.1indirecthigh12.2.2
uuid3.4.0indirecthigh113.0.1
micromatch2.3.11indirectmoderate14.0.8
micromatch3.1.10indirectmoderate14.0.8
qs6.5.5indirectmoderate26.16.0
request2.88.2indirectmoderate13.0.0
tough-cookie2.5.0indirectmoderate14.1.3

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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 statisticsGo, npm.