Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 19:29 UTC

MattCheramie / GopherTrunk

Pure-Go, cross-platform RTL-SDR scanner and audio processing toolkit.

GoApache-2.0★ 161 stars⑂ 21 forkssince May 2026View on GitHub ↗
KindNetwork serviceWeb interfaceTerminal interfacehow this is determined

MattCheramie/GopherTrunk holds a health index of 75 out of 100, placing it in the Good band. It scores highest on AI Readiness (87/100) and lowest on Security (40/100). It was last updated today. A single contributor accounts for most of its recent work.

75
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.

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

Ownership

Magic Matt Personal account
22 followers5 public repossince Jul 2012

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
Gogithub.com/MattCheramie/GopherTrunkv1.3.2-1230 days ago

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
17.3/36Commit cadence — 25/52 weeks with commits
18/18Commit volume — 3,147 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year3,147
human_commit_share1
days_since_last_push0
active_weeks_last_year25
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~1.9 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv1.3.2
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases1.9

Community & Adoption

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

63Moderate · 17% of overall
How it's scored
35.8/60Stars — 161 stars
10.8/25Forks — 21 forks
3.3/15Watchers — 5 watchers
Inputs used
forks21
stars161
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, goreportcard.com, shields.io
has_pull_request_templateyes

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 factor — 1 contributor(s) cover half of all commits
8.3/22.5Commit distribution — top contributor authored 63% of commits
4.1/13.5Contributor breadth — 3 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.632
How it's scored
31.3/42Issue resolution — 75% of issues closed
29.2/30PR acceptance — 1,136/1,166 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/11 approved changesets -- score normalized to 0
Inputs used
merged_prs1,136
open_issues31
closed_issues91
prs_merged_7d23
prs_decided_7d23
prs_merged_30d59
prs_decided_30d60
issue_closed_ratio0.746
closed_unmerged_prs30
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
9.8/25Owner reach — 22 followers of MattCheramie
17.7/25Track record — 5 public repos, account ~14 yr old
Inputs used
followers22
owner_typeUser
is_verified—
owner_loginMattCheramie
public_repos5
account_age_days5,220
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 0 days ago
20/20Version history — 123 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/MattCheramie/GopherTrunk
ecosystemsgo
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 12 topics
10/10Wiki
Inputs used
topicsgolang, open-source, rf, rtl-sdr, sdr, p25, tetra, d-star, dmr, edacs, ltr, nxdn
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?

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 11 out of 11 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/11 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
2/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 66 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4
Excluded from scoring (no data or not applicable): Packaging. 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.

87Excellent · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt present
40/40Legible commit history — 99 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url—
legible_history_share0.99
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes203,879
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — web/configbuilder/tsconfig.json, web/cryptolab/tsconfig.json, web/rfscope/tsconfig.json, web/siglab/tsconfig.json, web/tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 65 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
4/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum, package-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configsweb/configbuilder/tsconfig.json, web/cryptolab/tsconfig.json, web/rfscope/tsconfig.json, web/siglab/tsconfig.json, web/tsconfig.json
agent_commit_share0.65
toolchain_manifestsgo.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Go (statically typed)
54.7/55Manageable file sizes — 14/2,446 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes259,279
source_files_sampled2,446
oversized_source_files14
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — proto/audio.proto, proto/events.proto, proto/rid.proto, proto/system.proto, proto/talkgroup.proto
0/20MCP server
40/40Runnable examples — samples
Inputs used
example_dirssamples
has_mcp_signalno
api_schema_filesproto/audio.proto, proto/events.proto, proto/rid.proto, proto/system.proto, proto/talkgroup.proto
interfaces_expected_ofnetwork-service

Key facts

161GitHub stars
3contributors
3,147commits, last 12 months
0days since last push
100releases
1bus factor
31open 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

Star and fork history 0 ★ / 21 ⇿
0Stars
21Forks
94Releases

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.

048121620242122026-052026-072026-10
Major 1Minor 8Patch 85
OpenSSF Scorecard 4.0 / 10
4.0aggregate

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-10-21 19:28 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests11 out of 11 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/11 approved changesets -- score normalized to 0
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
10Maintained30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities66 existing vulnerabilities detected
Direct dependencies 26
RegistryPackageVersion constraintManifest
Gogopkg.in/yaml.v3v3.0.1go.mod
Gogithub.com/braheezy/shine-mp3v0.1.0go.mod
Gogithub.com/charmbracelet/bubblesv1.0.0go.mod
Gogithub.com/charmbracelet/bubbleteav1.3.10go.mod
Gogithub.com/charmbracelet/lipglossv1.1.0go.mod
Gogithub.com/charmbracelet/x/exp/teatestv0.0.0-20260511125431-fe5d686e0c99go.mod
Gogithub.com/ebitengine/oto/v3v3.3.3go.mod
Gogithub.com/ebitengine/puregov0.10.0go.mod
Gogithub.com/gorilla/websocketv1.5.3go.mod
Gogithub.com/ledongthuc/pdfv0.0.0-20250511090121-5959a4027728go.mod
Gogithub.com/mewkiz/flacv1.0.14go.mod
Gogithub.com/prometheus/client_golangv1.23.2go.mod
Gogolang.org/x/sysv0.48.0go.mod
Gogolang.org/x/textv0.42.0go.mod
Gogonum.org/v1/gonumv0.17.0go.mod
Gogoogle.golang.org/grpcv1.83.2go.mod
Gogoogle.golang.org/protobufv1.36.11go.mod
Gomodernc.org/sqlitev1.50.0go.mod
npmchart.js^4.4.5web/package.json
npmd3-scale^4.0.2web/package.json
npmleaflet^1.9.4web/package.json
npmreact^18.3.1web/package.json
npmreact-chartjs-2^5.2.0web/package.json
npmreact-dom^18.3.1web/package.json
npmreact-router-dom^6.27.0web/package.json
npmzustand^4.5.5web/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

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 — Go.