Public record
Software health reportschema 0.31.0 · metrics 2.5.0 · 2026-08-06 16:16 UTC

pubky / mainline

Simple, robust, BitTorrent's Mainline DHT implementation

RustMIT★ 101 stars⑂ 21 forkssince Oct 2023View on GitHub ↗
KindLibraryhow this is determined

pubky/mainline holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (81/100) and lowest on AI Readiness (43/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

PubkyOrganization
149 followers56 public repossince Jan 2024

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iomainline8.0.043,408432 days agobittorrentdhtkademliamainlinetorrentnetwork-programming

Metrics by category

Vitality

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

81Excellent · 21% of overall

Development activity

73Good
How it's scored
36/36Push recency — last push 2 days ago
11.8/36Commit cadence — 17/52 weeks with commits
15/18Commit volume — 46 commits in the last year
10/10OpenSSF Scorecard: Maintained — 14 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year46
human_commit_share1
days_since_last_push2
active_weeks_last_year17

Release discipline

92Excellent
How it's scored
27/27Ships releases — 12 releases published
36/36Release recency — latest release 2 days ago
19.8/27Release cadence — a release every ~68.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count12
latest_release_tagv8.0.0
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases68.1
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?

55Moderate · 17% of overall

Popularity & adoption

46Weak
How it's scored
32.4/60Stars — 101 stars
10.8/25Forks — 21 forks
2.7/15Watchers — 4 watchers
Inputs used
forks21
stars101
watchers4
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

Ecosystem adoption (downloads)

77Good
How it's scored
61.8/80Monthly downloads — 43,408 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesmainline
dependents—
ecosystemscrates
total_downloads408,968
monthly_downloads43,408
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

67Good · 23% of overall

Maintainer resilience (bus factor)

37Weak
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.4/22.5Commit distribution — top contributor authored 80% of commits
13.5/13.5Contributor breadth — 14 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled14
top_contributor_share0.803

Issue & PR responsiveness

81Excellent
How it's scored
30.7/42Issue resolution — 73% of issues closed
25.1/30PR acceptance — 72/86 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_prs72
open_issues7
closed_issues19
prs_merged_7d3
prs_decided_7d3
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.731
closed_unmerged_prs14
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

64Moderate
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
15.6/25Owner reach — 149 followers of pubky
18/25Track record — 56 public repos, account ~2 yr old
Inputs used
followers149
owner_typeOrganization
is_verified—
owner_loginpubky
public_repos56
account_age_days945

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on crates
35/35Publish recency — latest publish 2 days ago
20/20Version history — 43 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesmainline
ecosystemscrates
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall

Engineering practices

44Weak
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 25 out of 25 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
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—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

58Moderate · 16% of overall

Security posture

58Moderate
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
2.5/2.5CI-Tests — 25 out of 25 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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 6 contributing companies or organizations
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 — 14 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): signed_releases. 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.

43Weak · 4% of overall

Agent context & guidance

40Weak
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 95 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.95
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

26At Risk
How it's scored
12.6/18One-command bootstrap — Cargo.toml, docs/simulation/Cargo.toml (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.01
toolchain_manifestsCargo.toml, docs/simulation/Cargo.toml
dependency_bot_commit_share0

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — Rust (statically typed)
55/55Manageable file sizes — 0/38 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes50,968
source_files_sampled38
oversized_source_files0

Machine-readable interfaces

40Weak
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—

Key facts

101GitHub stars
14contributors
46commits, last 12 months
2days since last push
12releases
1bus factor
7open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index crates:mainline@8.0.0; advisories assessed against the repository dependency graph instead
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 21 ⇿
0Stars
21Forks
10Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

048121620242112023-122025-042026-08
Major 4Minor 3Patch 3

Each point covers 3 days.

OpenSSF Scorecard 5.8 / 10
5.8aggregate

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-08-06 16:16 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests25 out of 25 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained14 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 14
RegistryPackageVersion constraintManifest
crates.iogetrandom0.4Cargo.toml
crates.ioserde_bencode0.2.4Cargo.toml
crates.ioserde1.0.228Cargo.toml
crates.ioserde_bytes0.11.19Cargo.toml
crates.iothiserror2.0.18Cargo.toml
crates.iocrc3.4.0Cargo.toml
crates.iosha1_smol1.0.1Cargo.toml
crates.ioed25519-dalek3.0.0-pre.1Cargo.toml
crates.iotracing0.1.44Cargo.toml
crates.iolru0.16.2Cargo.toml
crates.iodyn-clone1.0.20Cargo.toml
crates.iodocument-features0.2.12Cargo.toml
crates.ioflume0.12.0Cargo.toml
crates.iofutures-lite2.6.1Cargo.toml
All dependencies 25

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

RegistryPackageVersionRelation
crates.iocrc—direct
crates.iodocument-features—direct
crates.iodyn-clone—direct
crates.ioed25519-dalek—direct
crates.ioflume—direct
crates.iofutures-lite—direct
crates.iogetrandom—direct
crates.iolru—direct
crates.ioserde—direct
crates.ioserde_bencode—direct
crates.ioserde_bytes—direct
crates.iosha1_smol—direct
crates.iothiserror—direct
crates.iotracing—direct
crates.ioclap—indirect
crates.iocolored—indirect
crates.ioctrlc—indirect
crates.iodashmap—indirect
crates.iofutures—indirect
crates.iohisto—indirect
crates.ionum_cpus—indirect
crates.ioplotters—indirect
crates.iorayon—indirect
crates.iostatrs—indirect
crates.iotracing-subscriber—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

Raw JSON report machine-readable

Related records

Inspected repositories sharing catalogue tags or ecosystems with pubky/mainline. Read them side by side →

62n0-computer/n0-mainlineSimple, robust, BitTorrent's Mainline DHT implementationModerate86pubky/pkarrPublic Key Addressable Resource Records (sovereign TLDs)Excellent63m0rf30/stremio-server-goUNOFFICIAL IPv6-capable, pure-Go drop-in for Stremio's streaming server (enginefs API): dual-stack torrents, with HLS transcoding and DLNA casting.Moderate81holochain/kitsune2p2p / dht communication frameworkExcellent81pubky/pubky-coreAn open protocol for per-public-key backends for censorship resistant web applications.Excellent75WithAutonomi/saorsa-coreSaorsa Core - P2P networking library with DHT, QUIC transport, four-word addresses, and MCP integrationGood

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.5.0, schema v0.31.0 — full methodology · metrics wiki.

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