Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 08:55 UTC

eriicafes / got

Fluent dependency injection in Go

GoMIT★ 1 star⑂ 1 forksince Feb 2025View on GitHub ↗

eriicafes/got holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on AI Readiness (51/100) and lowest on Community & Adoption (24/100). It was last updated 266 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Eric AfesPersonal account
18 followers52 public repossince May 2021

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/eriicafes/gotv0.3.0-3266 days ago

Metrics by category

Vitality

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

27At Risk · 21% of overall

Development activity

11Critical
How it's scored
3.6/36Push recency — last push 266 days ago
0.7/36Commit cadence — 1/52 weeks with commits
6.3/18Commit volume — 4 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year4
human_commit_share—
days_since_last_push266
active_weeks_last_year1

Release discipline

50Moderate
How it's scored
16.2/27Ships releases — 3 version tags (no GitHub releases)
16.2/36Release recency — latest release 266 days ago
12.6/27Release cadence — a release every ~151.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tagv0.3.0
releases_from_tagsyes
days_since_latest_release266
mean_days_between_releases151.7
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?

24At Risk · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 1 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars1
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges0
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?

50Moderate · 23% of overall

Maintainer resilience (bus factor)

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

Issue & PR responsiveness

67Good
How it's scored
0/42Issue resolution — no issues or no data
30/30PR acceptance — 3/3 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/8 approved changesets -- score normalized to 0
Inputs used
merged_prs3
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

53Moderate
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
9.2/25Owner reach — 18 followers of eriicafes
23.2/25Track record — 52 public repos, account ~5 yr old
Inputs used
followers18
owner_typeUser
is_verified—
owner_logineriicafes
public_repos52
account_age_days1,948
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

83Excellent
How it's scored
25/25Published & resolvable — 1 package(s) on go
26/35Publish recency — latest publish 266 days ago
12/20Version history — 3 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/eriicafes/got
ecosystemsgo
any_deprecatedno
min_days_since_publish266

Engineering Quality

Are baseline engineering and documentation practices in place?

49Weak · 19% of overall

Engineering practices

48Weak
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 3 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

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
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?

38Weak · 16% of overall

Security posture

23At Risk
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/8 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
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
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 10 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate2.3
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories10
affected_packages4
assessed_packages101
unassessed_packages0
affected_by_severityhigh 3, moderate 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 101 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.

51Moderate · 4% of overall

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

Verify loop (build / test / typecheck)

71Good
How it's scored
12.6/18One-command bootstrap — go.mod (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no data
0/8Automated maintenance — no data
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share—
toolchain_manifestsgo.mod
dependency_bot_commit_share—
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — Go (statically typed)
55/55Manageable file sizes — 0/2 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes10,121
source_files_sampled2
oversized_source_files0

Key facts

1GitHub stars
1contributors
4commits, last 12 months
266days since last push
3releases
1bus factor
0open issues
Go, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 2.3 / 10
2.3aggregate

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 08:55 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 3 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/8 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update 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
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
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
0Vulnerabilities10 existing vulnerabilities detected
All dependencies 101

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

RegistryPackageVersionRelation
npm@babel/runtime7.26.9indirect
npm@changesets/apply-release-plan7.0.10indirect
npm@changesets/assemble-release-plan6.0.6indirect
npm@changesets/changelog-git0.2.1indirect
npm@changesets/cli2.28.1indirect
npm@changesets/config3.1.1indirect
npm@changesets/errors0.2.0indirect
npm@changesets/get-dependents-graph2.1.3indirect
npm@changesets/get-release-plan4.0.8indirect
npm@changesets/get-version-range-type0.4.0indirect
npm@changesets/git3.0.2indirect
npm@changesets/logger0.1.1indirect
npm@changesets/parse0.4.1indirect
npm@changesets/pre2.0.2indirect
npm@changesets/read0.6.3indirect
npm@changesets/should-skip-package0.1.2indirect
npm@changesets/types4.1.0indirect
npm@changesets/types6.1.0indirect
npm@changesets/write0.4.0indirect
npm@manypkg/find-root1.1.0indirect
npm@manypkg/get-packages1.1.3indirect
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npm@types/node12.20.55indirect
npmansi-colors4.1.3indirect
npmansi-regex5.0.1indirect
npmargparse1.0.10indirect
npmarray-union2.1.0indirect
npmbetter-path-resolve1.0.0indirect
npmbraces3.0.3indirect
npmchardet0.7.0indirect
npmci-info3.9.0indirect
npmcross-spawn7.0.6indirect
npmdetect-indent6.1.0indirect
npmdir-glob3.0.1indirect
npmenquirer2.4.1indirect
npmesprima4.0.1indirect
npmextendable-error0.1.7indirect
npmexternal-editor3.1.0indirect
npmfast-glob3.3.3indirect
npmfastq1.19.1indirect
npmfill-range7.1.1indirect
npmfind-up4.1.0indirect
npmfs-extra7.0.1indirect
npmfs-extra8.1.0indirect
npmglob-parent5.1.2indirect
npmglobby11.1.0indirect
npmgraceful-fs4.2.11indirect
npmhuman-id4.1.1indirect
npmiconv-lite0.4.24indirect
npmignore5.3.2indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-subdir1.2.0indirect
npmis-windows1.0.2indirect
npmisexe2.0.0indirect
npmjs-yaml3.14.1indirect
npmjsonfile4.0.0indirect
npmlocate-path5.0.0indirect
npmlodash.startcase4.4.0indirect
npmmerge21.4.1indirect
npmmicromatch4.0.8indirect
npmmri1.2.0indirect
npmos-tmpdir1.0.2indirect
npmoutdent0.5.0indirect
npmp-filter2.1.0indirect
npmp-limit2.3.0indirect
npmp-locate4.1.0indirect
npmp-map2.1.0indirect
npmp-try2.2.0indirect
npmpackage-manager-detector0.2.9indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpath-type4.0.0indirect
npmpicocolors1.1.1indirect
npmpicomatch2.3.1indirect
npmpify4.0.1indirect
npmprettier2.8.8indirect
npmqueue-microtask1.2.3indirect
npmread-yaml-file1.1.0indirect
npmregenerator-runtime0.14.1indirect
npmresolve-from5.0.0indirect
npmreusify1.1.0indirect
npmrun-parallel1.2.0indirect
npmsafer-buffer2.1.2indirect
npmsemver7.7.1indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmslash3.0.0indirect
npmspawndamnit3.0.1indirect
npmsprintf-js1.0.3indirect
npmstrip-ansi6.0.1indirect
npmstrip-bom3.0.0indirect
npmterm-size2.2.1indirect
npmtmp0.0.33indirect
npmto-regex-range5.0.1indirect
npmuniversalify0.1.2indirect
npmwhich2.0.2indirect
Dependency advisories 4

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

PackageVersionRelationSeverityAdvisoriesFixed in
js-yaml3.14.1indirecthigh54.3.2
picomatch2.3.1indirecthigh24.0.4
tmp0.0.33indirecthigh20.2.6
@babel/runtime7.26.9indirectmoderate18.0.0-alpha.17

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with eriicafes/got. Read them side by side →

100mattermost/mattermostMattermost is an open source platform for secure collaboration across the entire software development lifecycle..Exceptional100coder/coderSecure environments for developers and their agentsExceptional100microsoft/onnxruntimeONNX Runtime: cross-platform, high performance ML inferencing and training acceleratorExceptional100authelia/autheliaThe Single Sign-On Multi-Factor portal for web apps. OpenID Certified™ and Post-Quantum Cryptography Ready.Exceptional100hashicorp/consulConsul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.Exceptional100go-gitea/giteaGit with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CDExceptional

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.