Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-31 18:07 UTC

slink-go / util

miscellaneous go utils

GoApache-2.0★ 0 stars⑂ 0 forkssince Jun 2024View on GitHub ↗

slink-go/util holds a health index of 14 out of 100, placing it in the Critical band. It scores highest on Vitality (57/100) and lowest on Community & Adoption (12/100). It was last updated 18 days ago. A single contributor accounts for most of its recent work.

overall / 100

Critical

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.

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)

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 33 is calibrated to 27 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 50% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

slinkOrganization

0 followers27 public repossince Jun 2023

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish
Go	go.slink.ws/util	v0.0.17	-	17	18 days ago

Metrics by category

Vitality

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

57Moderate · 21% of overall

Development activity

41Weak

How it's scored

28.8/36	Push recency — last push 18 days ago
3.5/36	Commit cadence — 5/52 weeks with commits
7.6/18	Commit volume — 6 commits in the last year
1/10	OpenSSF Scorecard: Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1

Inputs used

commits_last_year	6
human_commit_share	1
days_since_last_push	18
active_weeks_last_year	5

Release discipline

80Excellent

How it's scored

16.2/27	Ships releases — 17 version tags (no GitHub releases)
36/36	Release recency — latest release 18 days ago
19.8/27	Release cadence — a release every ~52.3 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	17
latest_release_tag	v0.0.17
releases_from_tags	yes
days_since_latest_release	18
mean_days_between_releases	52.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?

12Critical · 17% of overall

Popularity & adoption

1Critical

How it's scored

0/60	Stars — 0 stars
0/25	Forks — 0 forks
0/15	Watchers — 0 watchers

Inputs used

forks	0
stars	0
watchers	0
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

25At Risk

How it's scored

0/22.5	README
22.5/22.5	License — recognized license (Apache-2.0)
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	no
has_license	yes
readme_badges	—
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	no

Sustainability & Governance

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

38Weak · 23% of overall

Maintainer resilience (bus factor)

10Critical

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
0/22.5	Commit distribution — top contributor authored 100% of commits
1.4/13.5	Contributor breadth — 1 contributors
0/10	OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0

Inputs used

bus_factor	1
contributors_sampled	1
top_contributor_share	1

Issue & PR responsiveness

1Critical

How it's scored

0/42	Issue resolution — no issues or no data
0/30	PR acceptance — no decided pull requests or no data
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — Found 0/21 approved changesets -- score normalized to 0

Inputs used

merged_prs	0
open_issues	0
closed_issues	0
prs_merged_7d	—
prs_decided_7d	—
prs_merged_30d	—
prs_decided_30d	—
issue_closed_ratio	—
closed_unmerged_prs	0
first_time_authors_30d	—
first_time_prs_merged_30d	—
first_time_prs_decided_30d	—

Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

58Moderate

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain — verified-domain status not read for this organization
0/25	Owner reach — 0 followers of slink-go
16.8/25	Track record — 27 public repos, account ~3 yr old

Inputs used

followers	0
owner_type	Organization
is_verified	—
owner_login	slink-go
public_repos	27
account_age_days	1,138

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on go
35/35	Publish recency — latest publish 18 days ago
20/20	Version history — 17 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	go.slink.ws/util
ecosystems	go
any_deprecated	no
min_days_since_publish	18

Engineering Quality

Are baseline engineering and documentation practices in place?

26At Risk · 19% of overall

Engineering practices

30At Risk

How it's scored

0/24	CI workflows
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
0/20	OpenSSF Scorecard: CI-Tests — no data

Inputs used

has_ci	no
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

20At Risk

How it's scored

0/30	README
0/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

topics	—
has_wiki	yes
homepage	—
docs_site	—
has_readme	no
has_docs_dir	no
has_description	yes

Security

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

23At Risk · 16% of overall

Security posture

13Critical

Jurisdiction risk alert

High-risk jurisdiction exposure detected

1 top contributor profilesRussia

Based on self-published public profile locations. This governance signal does not determine nationality, citizenship, intent, sanctions status, or individual trustworthiness.

How jurisdiction exposure is assessed

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — branch protection not enabled on development/release branches
0/2.5	CI-Tests — no data
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 0/21 approved changesets -- score normalized to 0
0/2.5	Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10	Dangerous-Workflow — no data
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
0.8/7.5	Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
0/5	SAST — no SAST tool detected
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — no data
6.8/7.5	Vulnerabilities — 1 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	12
scorecard_version	v5.5.0
checks_inconclusive	6
scorecard_aggregate	2.6
high_risk_jurisdiction_cap	34
high_risk_jurisdiction_multiplier	50
security_posture_after_multiplier	13
security_posture_before_jurisdiction	26

Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 50% multiplier and gives Security posture an At risk ceiling of 34.

Dependency advisories

64Moderate

How it's scored

14/35	Direct dependencies free of known advisories — 1 affected: github.com/golang-jwt/jwt v3.2.2+incompatible (high 7.5)
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
33.7/40	No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 496 days ago

Inputs used

source	osv
advisories	2
affected_packages	1
assessed_packages	15
unassessed_packages	0
affected_by_severity	high 1
direct_affected_packages	1

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 15 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.

47Weak · 4% of overall

Agent context & guidance

1Critical

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
0/40	Legible commit history — 0 of 21 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

62Moderate

How it's scored

12.6/18	One-command bootstrap — go.mod (toolchain convention, no task runner)
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — Go (statically typed)
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 21
0/8	Automated maintenance — no automated dependency updates observed
0/10	OpenSSF Scorecard: Pinned-Dependencies — no data

Inputs used

has_nix	no
has_tests	yes
lockfiles	go.sum
has_dockerfile	no
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	—
agent_commit_share	0
toolchain_manifests	go.mod
dependency_bot_commit_share	0

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — Go (statically typed)
55/55	Manageable file sizes — 0/17 source files over 60KB

Inputs used

primary_language	Go
largest_source_bytes	3,527
source_files_sampled	17
oversized_source_files	0

Key facts

0GitHub stars

1contributors

6commits, last 12 months

18days since last push

17releases

1bus factor

0open issues

Gopackage ecosystems

More detail

OpenSSF Scorecard 2.6 / 10

2.6aggregate

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-07-31 18:07 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
n/a	CI-Tests	no pull request found
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 0/21 approved changesets -- score normalized to 0
0	Contributors	project has 0 contributing companies or organizations -- score normalized to 0
n/a	Dangerous-Workflow	no workflows found
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
1	Maintained	2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
n/a	Packaging	packaging workflow not detected
n/a	Pinned-Dependencies	no dependencies found
0	SAST	no SAST tool detected
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
n/a	Token-Permissions	No tokens found
9	Vulnerabilities	1 existing vulnerabilities detected

Direct dependencies 5

Registry	Package	Version constraint	Manifest
Go	github.com/golang-jwt/jwt	`v3.2.2+incompatible`	go.mod
Go	github.com/google/uuid	`v1.6.0`	go.mod
Go	github.com/stretchr/testify	`v1.11.1`	go.mod
Go	github.com/xhit/go-str2duration/v2	`v2.1.0`	go.mod
Go	go.slink.ws/logging	`v0.0.17`	go.mod

All dependencies 15

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

Registry	Package	Version	Relation
Go	github.com/golang-jwt/jwt	`v3.2.2+incompatible`	direct
Go	github.com/google/uuid	`v1.6.0`	direct
Go	github.com/stretchr/testify	`v1.11.1`	direct
Go	github.com/xhit/go-str2duration/v2	`v2.1.0`	direct
Go	go.slink.ws/logging	`v0.0.17`	direct
Go	github.com/davecgh/go-spew	`v1.1.2-0.20180830191138-d8f796af33cc`	indirect
Go	github.com/kr/pretty	`v0.3.1`	indirect
Go	github.com/mattn/go-colorable	`v0.1.15`	indirect
Go	github.com/mattn/go-isatty	`v0.0.22`	indirect
Go	github.com/pmezard/go-difflib	`v1.0.1-0.20181226105442-5d4384ee4fb2`	indirect
Go	github.com/rogpeppe/go-internal	`v1.14.1`	indirect
Go	github.com/rs/zerolog	`v1.35.1`	indirect
Go	golang.org/x/sys	`v0.47.0`	indirect
Go	gopkg.in/check.v1	`v1.0.0-20201130134442-10cb98267c6c`	indirect
Go	gopkg.in/yaml.v3	`v3.0.1`	indirect

Dependency advisories 1

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

Package	Version	Relation	Severity	Advisories	Fixed in
github.com/golang-jwt/jwt	`v3.2.2+incompatible`	direct	high	2	`5.2.2`

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.

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

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

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

More detail

Feedback

Related records