Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 05:39 UTC

nemikon / goround

GoMIT★ 1 star⑂ 0 forkssince Jul 2025View on GitHub ↗

nemikon/goround holds a health index of 23 out of 100, placing it in the At Risk band. It scores highest on AI Readiness (58/100) and lowest on Security (1/100). It was last updated 53 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

nemikonPersonal account
1 follower1 public reposince Jul 2025

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/nemikon/goroundv0.0.2-253 days ago

Metrics by category

Vitality

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

44Weak · 21% of overall
How it's scored
18/36Push recencylast push 53 days ago
0.7/36Commit cadence1/52 weeks with commits
4.3/18Commit volume2 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year2
human_commit_share
days_since_last_push53
active_weeks_last_year1
How it's scored
16.2/27Ships releases2 version tags (no GitHub releases)
36/36Release recencylatest release 53 days ago
12.6/27Release cadencea release every ~318.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count2
latest_release_tagv0.0.2
releases_from_tagsyes
days_since_latest_release53
mean_days_between_releases318.3

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 (MIT)
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?

36Weak · 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
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
2.2/25Owner reach1 followers of nemikon
4.5/25Track record1 public repos, account ~1 yr old
Inputs used
followers1
owner_typeUser
is_verified
owner_loginnemikon
public_repos1
account_age_days425
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on go
35/35Publish recencylatest publish 53 days ago
12/20Version history2 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/nemikon/goround
ecosystemsgo
any_deprecatedno
min_days_since_publish53

Engineering Quality

Are baseline engineering and documentation practices in place?

36Weak · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

1Critical
How it's scored
0/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_site
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

1Critical · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfilespublished library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesgo.sum
manifestsgo.mod
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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.

58Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno 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.
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
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.
How it's scored
45/45Type-checkable codeGo (statically typed)
55/55Manageable file sizes0/4 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes14,630
source_files_sampled4
oversized_source_files0

Key facts

1GitHub stars
1contributors
2commits, last 12 months
53days since last push
2releases
1bus factor
0open issues
Gopackage 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
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/nemikon/goround: run: RepoClient.LocalPath: error during tarballHandler.setup: internal error: handler.httpClient.Do: Get "https://codeload.github.com/nemikon/goround/legacy.tar.gz/refs/heads/main": internal error: innerTransport.RoundTrip: internal error: innerTransport.RoundTrip: error in HTTP: dial tcp: lookup codeload.github.com on 127.0.0.11:53: server misbehaving); skipping Scorecard checks

More detail

Direct dependencies 1
RegistryPackageVersion constraintManifest
Gogithub.com/stretchr/testifyv1.10.0go.mod
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 statisticsGo.