Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-15 10:19 UTC

42atomys / webhooked

A webhook receiver on steroids.

GoMIT★ 43 stars⑂ 1 forksince Feb 2022View on GitHub ↗
KindCommand-line toolhow this is determined

42atomys/webhooked holds a health index of 29 out of 100, placing it in the At Risk band. It scores highest on AI Readiness (70/100) and lowest on Vitality (23/100). It was last updated 351 days ago. A single contributor accounts for most of its recent work.

29
overall / 100
At Risk

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.

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

Ownership

AtomysPersonal account
824 followers39 public repossince Aug 2014@go-sprout

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

Metrics by category

Vitality

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

23At Risk · 21% of overall
How it's scored
3.6/36Push recencylast push 351 days ago
0.7/36Commit cadence1/52 weeks with commits
2.7/18Commit volume1 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_year1
human_commit_share0.26
days_since_last_push351
active_weeks_last_year1
How it's scored
27/27Ships releases15 releases published
0/36Release recencylatest release 890 days ago
19.8/27Release cadencea release every ~80.6 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count15
latest_release_tagv0.8
releases_from_tagsno
days_since_latest_release890
mean_days_between_releases80.6

Community & Adoption

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

47Weak · 17% of overall
How it's scored
26.3/60Stars43 stars
0/25Forks1 forks
0/15Watchers2 watchers
Inputs used
forks1
stars43
watchers2
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
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges10
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, goreportcard.com, pkg.go.dev, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

52Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1/22.5Commit distributiontop contributor authored 96% of commits
2.7/13.5Contributor breadth2 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.957
How it's scored
40.7/42Issue resolution97% of issues closed
25.3/30PR acceptance129/153 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/5 approved changesets -- score normalized to 0
Inputs used
merged_prs129
open_issues1
closed_issues31
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.969
closed_unmerged_prs24
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
21/25Owner reach824 followers of 42atomys
23.7/25Track record39 public repos, account ~12 yr old
Inputs used
followers824
owner_typeUser
is_verified
owner_login42atomys
public_repos39
account_age_days4,383
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

63Moderate · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 27 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

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsgolang, webhooks, hacktoberfest, apps
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?

56Moderate · 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 27 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/5 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
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
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
3.5/5SASTSAST tool detected but not run on all commits
2/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.5
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages31
unassessed_packages0
affected_by_severityunknown 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 31 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

70Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history26 of 26 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentdevcontainer, Dockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance74 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
lockfilesgo.sum
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile
has_devcontaineryes
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsgo.mod
dependency_bot_commit_share0.74
How it's scored
45/45Type-checkable codeGo (statically typed)
55/55Manageable file sizes0/56 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes12,115
source_files_sampled56
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

43GitHub stars
2contributors
1commits, last 12 months
351days since last push
15releases
1bus factor
1open issues
Gopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch go package 'atomys.codes/webhooked' from its registry

More detail

OpenSSF Scorecard 4.5 / 10
4.5aggregate

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

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 27 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/5 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
7SASTSAST tool detected but not run on all commits
4Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
Gogithub.com/go-redis/redis/v8v8.11.5go.mod
Gogithub.com/gorilla/muxv1.8.1go.mod
Gogithub.com/jmoiron/sqlxv1.3.5go.mod
Gogithub.com/knadh/koanfv1.5.0go.mod
Gogithub.com/lib/pqv1.10.9go.mod
Gogithub.com/mitchellh/mapstructurev1.5.0go.mod
Gogithub.com/prometheus/client_golangv1.18.0go.mod
Gogithub.com/rs/zerologv1.32.0go.mod
Gogithub.com/spf13/cobrav1.8.0go.mod
Gogithub.com/streadway/amqpv1.1.0go.mod
Gogithub.com/stretchr/testifyv1.9.0go.mod
All dependencies 31

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

RegistryPackageVersionRelation
Gogithub.com/go-redis/redis/v88.11.5direct
Gogithub.com/gorilla/mux1.8.1direct
Gogithub.com/jmoiron/sqlx1.3.5direct
Gogithub.com/knadh/koanf1.5.0direct
Gogithub.com/lib/pq1.10.9direct
Gogithub.com/mitchellh/mapstructure1.5.0direct
Gogithub.com/prometheus/client_golang1.18.0direct
Gogithub.com/rs/zerolog1.32.0direct
Gogithub.com/spf13/cobra1.8.0direct
Gogithub.com/streadway/amqp1.1.0direct
Gogithub.com/stretchr/testify1.9.0direct
Gogithub.com/beorn7/perks1.0.1indirect
Gogithub.com/cespare/xxhash/v22.2.0indirect
Gogithub.com/davecgh/go-spew1.1.1indirect
Gogithub.com/dgryski/go-rendezvous0.0.0-20200823014737-9f7001d12a5findirect
Gogithub.com/fsnotify/fsnotify1.6.0indirect
Gogithub.com/inconshreveable/mousetrap1.1.0indirect
Gogithub.com/kr/text0.2.0indirect
Gogithub.com/mattn/go-colorable0.1.13indirect
Gogithub.com/mattn/go-isatty0.0.19indirect
Gogithub.com/matttproud/golang_protobuf_extensions/v22.0.0indirect
Gogithub.com/mitchellh/copystructure1.2.0indirect
Gogithub.com/mitchellh/reflectwalk1.0.2indirect
Gogithub.com/pmezard/go-difflib1.0.0indirect
Gogithub.com/prometheus/client_model0.5.0indirect
Gogithub.com/prometheus/common0.45.0indirect
Gogithub.com/prometheus/procfs0.12.0indirect
Gogithub.com/spf13/pflag1.0.5indirect
Gogolang.org/x/sys0.15.0indirect
Gogoogle.golang.org/protobuf1.33.0indirect
Gogopkg.in/yaml.v33.0.1indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 31 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
golang.org/x/sys0.15.0indirectunknown10.44.0

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.31.0 — full methodology · metrics wiki.

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