Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 03:43 UTC

1Money-Co / 1money-protocol-go-sdk

GoApache-2.0★ 0 stars⑂ 0 forkssince Mar 2025View on GitHub ↗

1Money-Co/1money-protocol-go-sdk holds a health index of 50 out of 100, placing it in the Moderate band. It scores highest on AI Readiness (81/100) and lowest on Community & Adoption (24/100). It was last updated 23 days ago. 2 contributors account for most of its recent work.

50
overall / 100
Moderate

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.

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

Ownership

1Money CoOrganization
5 followers10 public repossince May 2024

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/1Money-Co/1money-protocol-go-sdkv1.3.0-1738 days ago

Metrics by category

Vitality

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

67Good · 21% of overall
How it's scored
28.8/36Push recency — last push 23 days ago
6.2/36Commit cadence — 9/52 weeks with commits
11.3/18Commit volume — 17 commits in the last year
4/10OpenSSF Scorecard: Maintained — 4 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year17
human_commit_share1
days_since_last_push23
active_weeks_last_year9
How it's scored
27/27Ships releases — 16 releases published
36/36Release recency — latest release 38 days ago
19.8/27Release cadence — a release every ~46 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count16
latest_release_tagv1.3.0
releases_from_tagsno
days_since_latest_release38
mean_days_between_releases46
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
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
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgoreportcard.com, pkg.go.dev, shields.io
has_pull_request_templateno

Sustainability & Governance

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

69Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.8/22.5Commit distribution — top contributor authored 43% of commits
4.1/13.5Contributor breadth — 3 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor2
contributors_sampled3
top_contributor_share0.429
How it's scored
42/42Issue resolution — 100% of issues closed
28.5/30PR acceptance — 19/20 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs19
open_issues0
closed_issues4
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio1
closed_unmerged_prs1
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
30/30Ownership backing — organization-owned
0/20Verified domain
5.6/25Owner reach — 5 followers of 1Money-Co
12.2/25Track record — 10 public repos, account ~2 yr old
Inputs used
followers5
owner_typeOrganization
is_verifiedno
owner_login1Money-Co
public_repos10
account_age_days852

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 38 days ago
20/20Version history — 17 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/1Money-Co/1money-protocol-go-sdk
ecosystemsgo
any_deprecatedno
min_days_since_publish38

Engineering Quality

Are baseline engineering and documentation practices in place?

30At Risk · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 17 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

41Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — 0 out of 17 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
7.5/7.5Code-Review — all changesets reviewed
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
3/7.5Maintained — 4 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 4
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
0/7.5Vulnerabilities — 26 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.5
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: github.com/ethereum/go-ethereum 1.15.7 (high 7.5)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 248 days ago
Inputs used
sourceosv
advisories46
affected_packages3
assessed_packages9
unassessed_packages0
affected_by_severitycritical 1, high 1, unknown 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 9 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.

81Excellent · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
26.7/40Legible commit history — 28 of 56 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.5
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes2,556
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
10/10Demonstrated agent practice — 3 of the last 56 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.054
toolchain_manifestsgo.mod
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — Go (statically typed)
55/55Manageable file sizes — 0/44 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes56,992
source_files_sampled44
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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

0GitHub stars
3contributors
17commits, last 12 months
23days since last push
16releases
2bus factor
0open issues
Gopackage ecosystems

More detail

OpenSSF Scorecard 3.5 / 10
3.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-09-19 03:43 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 17 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
4Maintained4 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 4
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities26 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
Gogithub.com/ethereum/go-ethereumv1.15.7go.mod
Gogithub.com/stretchr/testifyv1.10.0go.mod
All dependencies 9

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

RegistryPackageVersionRelation
Gogithub.com/ethereum/go-ethereum1.15.7direct
Gogithub.com/stretchr/testify1.10.0direct
Gogithub.com/davecgh/go-spew1.1.1indirect
Gogithub.com/decred/dcrd/dcrec/secp256k1/v44.4.0indirect
Gogithub.com/holiman/uint2561.3.2indirect
Gogithub.com/pmezard/go-difflib1.0.0indirect
Gogolang.org/x/crypto0.36.0indirect
Gogolang.org/x/sys0.31.0indirect
Gogopkg.in/yaml.v33.0.1indirect
Dependency advisories 3

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

PackageVersionRelationSeverityAdvisoriesFixed in
golang.org/x/crypto0.36.0indirectcritical350.56.0
github.com/ethereum/go-ethereum1.15.7directhigh101.17.0
golang.org/x/sys0.31.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.34.0 — full methodology · metrics wiki.

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