Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-15 16:11 UTC

MixinNetwork / mixin

🚀 The Mixin-BFT-DAG network reference implementation.

GoGPL-3.0★ 520 stars⑂ 144 forkssince Apr 2018View on GitHub ↗
KindCommand-line toolhow this is determined

MixinNetwork/mixin holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (90/100) and lowest on AI Readiness (59/100). It was last updated today. A single contributor accounts for most of its recent work.

88
overall / 100
Excellent

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.

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

Ownership

Mixin NetworkOrganization
348 followers93 public repossince Nov 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/MixinNetwork/mixinv0.19.0-2782 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
36/36Push recencylast push 0 days ago
12.5/36Commit cadence18/52 weeks with commits
16.1/18Commit volume61 commits in the last year
10/10OpenSSF Scorecard: Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year61
human_commit_share
days_since_last_push0
active_weeks_last_year18
How it's scored
27/27Ships releases100 releases published
0/36Release recencylatest release 989 days ago
27/27Release cadencea release every ~9 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv0.16.10
releases_from_tagsno
days_since_latest_release989
mean_days_between_releases9

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

78Good · 17% of overall
How it's scored
44/60Stars520 stars
18/25Forks144 forks
9.4/15Watchers51 watchers
Inputs used
forks144
stars520
watchers51
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (GPL-3.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

72Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.7/22.5Commit distributiontop contributor authored 62% of commits
13.5/13.5Contributor breadth28 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled28
top_contributor_share0.615
How it's scored
36.5/42Issue resolution87% of issues closed
25/30PR acceptance95/114 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/29 approved changesets -- score normalized to 0
Inputs used
merged_prs95
open_issues9
closed_issues59
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.868
closed_unmerged_prs19
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
18.3/25Owner reach348 followers of MixinNetwork
25/25Track record93 public repos, account ~8 yr old
Inputs used
followers348
owner_typeOrganization
is_verified
owner_loginMixinNetwork
public_repos93
account_age_days3,175
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on go
35/35Publish recencylatest publish 2 days ago
20/20Version history278 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/MixinNetwork/mixin
ecosystemsgo
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.flake8, .golangci.yaml, .golangci.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests2 out of 2 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

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://mixin.one/assets/Mixin-Draft-2018-07-01.pdf
10/10Repository description
10/10Topics7 topics
10/10Wiki
Inputs used
topicsblockchain, bitcoin, dag, bft, lightning-network, mixin, mixinnetwork
has_wikiyes
homepagehttps://mixin.one/assets/Mixin-Draft-2018-07-01.pdf
docs_sitehttps://mixin.one/assets/Mixin-Draft-2018-07-01.pdf
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

64Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/29 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.4
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. 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.

59Moderate · 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, vendor/github.com/dgraph-io/badger/v4/Makefile, vendor/github.com/pelletier/go-toml/Makefile, vendor/github.com/urfave/cli/v2/Makefile, vendor/github.com/zeebo/blake3/Makefile
22/22Automated tests
11/11Lint / format config.flake8, .golangci.yaml, .golangci.yml
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile, vendor/github.com/dgraph-io/badger/v4/Makefile, vendor/github.com/pelletier/go-toml/Makefile, vendor/github.com/urfave/cli/v2/Makefile, vendor/github.com/zeebo/blake3/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
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)
54.7/55Manageable file sizes1/160 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes64,118
source_files_sampled160
oversized_source_files1
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)vendor/github.com/dgraph-io/badger/v4/pb/badgerpb4.proto
0/20MCP servernot applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalno
api_schema_filesvendor/github.com/dgraph-io/badger/v4/pb/badgerpb4.proto
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

520GitHub stars
28contributors
61commits, last 12 months
0days since last push
100releases
1bus factor
9open issues
Gopackage ecosystems

More detail

OpenSSF Scorecard 6.4 / 10
6.4aggregate

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-15 16:11 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests2 out of 2 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/29 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
Gofilippo.io/edwards25519v1.2.0go.mod
Gogithub.com/dgraph-io/badger/v4v4.9.4go.mod
Gogithub.com/dgraph-io/ristretto/v2v2.4.2go.mod
Gogithub.com/pelletier/go-tomlv1.9.5go.mod
Gogithub.com/quic-go/quic-gov0.60.0go.mod
Gogithub.com/shopspring/decimalv1.4.0go.mod
Gogithub.com/stretchr/testifyv1.11.1go.mod
Gogithub.com/urfave/cli/v2v2.27.7go.mod
Gogithub.com/zeebo/blake3v0.2.4go.mod
Gogolang.org/x/cryptov0.54.0go.mod
All dependencies 23

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

RegistryPackageVersionRelation
Gofilippo.io/edwards25519v1.2.0direct
Gogithub.com/dgraph-io/ristretto/v2v2.4.2direct
Gogithub.com/pelletier/go-tomlv1.9.5direct
Gogithub.com/quic-go/quic-gov0.60.0direct
Gogithub.com/shopspring/decimalv1.4.0direct
Gogithub.com/stretchr/testifyv1.11.1direct
Gogithub.com/urfave/cli/v2v2.27.7direct
Gogithub.com/zeebo/blake3v0.2.4direct
Gogolang.org/x/cryptov0.54.0direct
Gogithub.com/cespare/xxhash/v2v2.3.0indirect
Gogithub.com/cpuguy83/go-md2man/v2v2.0.7indirect
Gogithub.com/davecgh/go-spewv1.1.1indirect
Gogithub.com/dustin/go-humanizev1.0.1indirect
Gogithub.com/google/flatbuffersv25.12.19+incompatibleindirect
Gogithub.com/klauspost/compressv1.19.0indirect
Gogithub.com/klauspost/cpuid/v2v2.4.0indirect
Gogithub.com/pmezard/go-difflibv1.0.0indirect
Gogithub.com/russross/blackfriday/v2v2.1.0indirect
Gogithub.com/xrash/smetricsv0.0.0-20250705151800-55b8f293f342indirect
Gogolang.org/x/netv0.57.0indirect
Gogolang.org/x/sysv0.47.0indirect
Gogoogle.golang.org/protobufv1.36.11indirect
Gogopkg.in/yaml.v3v3.0.1indirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsGo.