Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 07:59 UTC

hadron-memory / hadron-cli

Hadron CLI

GoMIT★ 0 stars⑂ 0 forkssince Jun 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

hadron-memory/hadron-cli holds a health index of 67 out of 100, placing it in the Good band. It scores highest on AI Readiness (86/100) and lowest on Community & Adoption (24/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Hadron MemoryOrganization
0 followers30 public repossince Mar 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/hadron-memory/hadron-cliv0.13.0-170 days ago

Metrics by category

Vitality

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

84Excellent · 21% of overall

Development activity

74Good
How it's scored
36/36Push recency — last push 0 days ago
9.7/36Commit cadence — 14/52 weeks with commits
18/18Commit volume — 307 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year307
human_commit_share1
days_since_last_push0
active_weeks_last_year14

Release discipline

98Exceptional
How it's scored
27/27Ships releases — 17 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~7.7 days
8/10OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count17
latest_release_tagv0.13.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases7.7

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 — 0 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars0
watchers0
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?

54Moderate · 23% of overall

Maintainer resilience (bus factor)

18Critical
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.2/22.5Commit distribution — top contributor authored 99% of commits
2.7/13.5Contributor breadth — 2 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.993

Issue & PR responsiveness

73Good
How it's scored
33.9/42Issue resolution — 81% of issues closed
29.4/30PR acceptance — 296/302 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs296
open_issues53
closed_issues221
prs_merged_7d16
prs_decided_7d16
prs_merged_30d59
prs_decided_30d60
issue_closed_ratio0.807
closed_unmerged_prs6
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.

Ownership & stewardship

42Weak
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
0/25Owner reach — 0 followers of hadron-memory
11.8/25Track record — 30 public repos, account ~0 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginhadron-memory
public_repos30
account_age_days177

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 — 17 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/hadron-memory/hadron-cli
ecosystemsgo
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall

Engineering practices

84Excellent
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — .golangci.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

75Good
How it's scored
30/30README
25/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_diryes
has_descriptionyes

Security

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

50Moderate · 16% of overall

Security posture

50Moderate
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
2.5/2.5CI-Tests — 30 out of 30 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/30 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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 28 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
6/7.5Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
5.2/7.5Vulnerabilities — 3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate5

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.

86Excellent · 4% of overall

Agent context & guidance

85Excellent
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes10,176

Verify loop (build / test / typecheck)

92Excellent
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — .golangci.yml
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 95 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.95
toolchain_manifestsgo.mod
dependency_bot_commit_share0

Code legibility for models

99Exceptional
How it's scored
45/45Type-checkable code — Go (statically typed)
53.9/55Manageable file sizes — 8/398 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes1,236,208
source_files_sampled398
oversized_source_files8

Machine-readable interfaces

60Moderate
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — internal/api/queries/access.graphql, internal/api/queries/agent.graphql, internal/api/queries/aiconfigs.graphql, internal/api/queries/apps.graphql, internal/api/queries/assets.graphql, internal/api/queries/assets_write.graphql, internal/api/queries/auth.graphql, internal/api/queries/chat.graphql, internal/api/queries/connections.graphql, internal/api/queries/grants.graphql, internal/api/queries/impersonation.graphql, internal/api/queries/mcpservers.graphql, internal/api/queries/me.graphql, internal/api/queries/memories.graphql, internal/api/queries/memory_access.graphql, internal/api/queries/nodes.graphql, internal/api/queries/objects.graphql, internal/api/queries/org.graphql, internal/api/queries/revisions.graphql, internal/api/queries/runs.graphql, internal/api/queries/search.graphql, internal/api/queries/secrets.graphql, internal/api/queries/server.graphql, internal/api/queries/tasks.graphql, internal/api/queries/team.graphql, schema/schema.graphql
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalyes
api_schema_filesinternal/api/queries/access.graphql, internal/api/queries/agent.graphql, internal/api/queries/aiconfigs.graphql, internal/api/queries/apps.graphql, internal/api/queries/assets.graphql, internal/api/queries/assets_write.graphql, internal/api/queries/auth.graphql, internal/api/queries/chat.graphql, internal/api/queries/connections.graphql, internal/api/queries/grants.graphql, internal/api/queries/impersonation.graphql, internal/api/queries/mcpservers.graphql, internal/api/queries/me.graphql, internal/api/queries/memories.graphql, internal/api/queries/memory_access.graphql, internal/api/queries/nodes.graphql, internal/api/queries/objects.graphql, internal/api/queries/org.graphql, internal/api/queries/revisions.graphql, internal/api/queries/runs.graphql, internal/api/queries/search.graphql, internal/api/queries/secrets.graphql, internal/api/queries/server.graphql, internal/api/queries/tasks.graphql, internal/api/queries/team.graphql, schema/schema.graphql
interfaces_expected_of—

Key facts

0GitHub stars
2contributors
307commits, last 12 months
0days since last push
17releases
1bus factor
53open issues
Gopackage ecosystems

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 5.0 / 10
5.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-09-11 07:58 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests30 out of 30 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/30 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 28 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 14
RegistryPackageVersion constraintManifest
Gogithub.com/Khan/genqlientv0.8.1go.mod
Gogithub.com/bmatcuk/doublestar/v4v4.6.1go.mod
Gogithub.com/gofrs/flockv0.13.0go.mod
Gogithub.com/google/uuidv1.6.0go.mod
Gogithub.com/hadron-memory/urn-lib-gov0.0.13go.mod
Gogithub.com/mattn/go-isattyv0.0.22go.mod
Gogithub.com/pelletier/go-toml/v2v2.2.4go.mod
Gogithub.com/spf13/cobrav1.10.2go.mod
Gogithub.com/spf13/pflagv1.0.10go.mod
Gogithub.com/spf13/viperv1.21.0go.mod
Gogithub.com/vektah/gqlparser/v2v2.5.19go.mod
Gogithub.com/zalando/go-keyringv0.2.8go.mod
Gogo.yaml.in/yaml/v3v3.0.4go.mod
Gogolang.org/x/termv0.37.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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with hadron-memory/hadron-cli. Read them side by side →

100stacklok/toolhiveToolHive is an enterprise-grade platform for running and managing Model Context Protocol (MCP) servers.Exceptional100pingcap/tidbTiDB is built for agentic workloads that grow unpredictably, with ACID guarantees and native support for transactions, analytics, and vector search. No data silos. No noisy neighbors. No infrastructure ceiling.Exceptional100apache/airflowApache Airflow - A platform to programmatically author, schedule, and monitor workflowsExceptional100hashicorp/consulConsul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.Exceptional100openfga/openfgaA high performance and flexible authorization/permission engine built for developers and inspired by Google ZanzibarExceptional100prometheus/prometheusThe Prometheus monitoring system and time series database.Exceptional

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.