Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 17:20 UTC

blueshift-gg / zeropod

Zero-copy, alignment-1 pod types for Solana programs

RustApache-2.0★ 4 stars⑂ 6 forkssince Apr 2026View on GitHub ↗

blueshift-gg/zeropod holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (83/100) and lowest on Community & Adoption (39/100). It was last updated 3 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

blueshiftOrganization
247 followers100 public repossince Jan 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
crates.iozeropod0.3.63,31293 days ago
crates.iozeropod-derive0.3.63,32793 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
9/36Commit cadence13/52 weeks with commits
15.6/18Commit volume54 commits in the last year
10/10OpenSSF Scorecard: Maintained28 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year54
human_commit_share1
days_since_last_push3
active_weeks_last_year13

Release discipline

100Exceptional
How it's scored
27/27Ships releases4 releases published
36/36Release recencylatest release 3 days ago
27/27Release cadencea release every ~41.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count4
latest_release_tagv0.3.6
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases41.9
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?

39Weak · 17% of overall
How it's scored
7.7/60Stars4 stars
5.8/25Forks6 forks
0/15Watchers0 watchers
Inputs used
forks6
stars4
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
51/80Monthly downloads6,639 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageszeropod, zeropod-derive
dependents
ecosystemscrates
total_downloads26,967
monthly_downloads6,639
unverified_packages_excluded
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?

69Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.7/22.5Commit distributiontop contributor authored 48% of commits
10.8/13.5Contributor breadth8 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor2
contributors_sampled8
top_contributor_share0.481
How it's scored
42/42Issue resolution100% of issues closed
21.4/30PR acceptance20/28 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 9/19 approved changesets -- score normalized to 4
Inputs used
merged_prs20
open_issues0
closed_issues2
prs_merged_7d2
prs_decided_7d4
prs_merged_30d2
prs_decided_30d4
issue_closed_ratio1
closed_unmerged_prs8
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
17.2/25Owner reach247 followers of blueshift-gg
16.4/25Track record100 public repos, account ~1 yr old
Inputs used
followers247
owner_typeOrganization
is_verifiedno
owner_loginblueshift-gg
public_repos100
account_age_days615

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on crates
35/35Publish recencylatest publish 3 days ago
20/20Version history9 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageszeropod, zeropod-derive
ecosystemscrates
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configzeropod/Cargo.toml ([lints])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests11 out of 11 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
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/zeropod
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_sitehttps://docs.rs/zeropod
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

70Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests11 out of 11 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
3/7.5Code-ReviewFound 9/19 approved changesets -- score normalized to 4
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
5/5Fuzzingproject is fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained28 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.2
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages29
unassessed_packages6
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 29 resolved dependencies against OSV. 6 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

67Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history51 of 54 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.944
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml, fuzz/Cargo.toml, zeropod-derive/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format configzeropod/Cargo.toml ([lints])
11/11Static type checkingRust (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 54
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml, fuzz/Cargo.toml, zeropod-derive/Cargo.toml, zeropod/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
55/55Manageable file sizes0/36 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes49,912
source_files_sampled36
oversized_source_files0

Key facts

4GitHub stars
8contributors
54commits, last 12 months
3days since last push
4releases
2bus factor
0open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 6 ⇿
0Stars
6Forks
3Releases

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.

123456622026-042026-062026-09
Major 0Minor 0Patch 3
OpenSSF Scorecard 6.2 / 10
6.2aggregate

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-18 17:20 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests11 out of 11 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 9/19 approved changesets -- score normalized to 4
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained28 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
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 7
RegistryPackageVersion constraintManifest
crates.ioproc-macro21zeropod-derive/Cargo.toml
crates.ioquote1zeropod-derive/Cargo.toml
crates.iosyn2zeropod-derive/Cargo.toml
crates.iozeropod-derivezeropod/Cargo.toml
crates.iowincode0.5.5zeropod/Cargo.toml
crates.iosolana-address>= 2.2, <2.7zeropod/Cargo.toml
crates.iosolana-program-error>=1.0, <4.0zeropod/Cargo.toml
All dependencies 35

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

RegistryPackageVersionRelation
crates.ioproc-macro2direct
crates.ioproc-macro21.0.106direct
crates.ioproc-macro21.0.107direct
crates.ioquotedirect
crates.ioquote1.0.46direct
crates.ioquote1.0.47direct
crates.iosolana-addressdirect
crates.iosolana-address2.6.1direct
crates.iosolana-program-errordirect
crates.iosolana-program-error3.0.1direct
crates.iosyndirect
crates.iosyn2.0.118direct
crates.iosyn2.0.119direct
crates.iowincodedirect
crates.iowincode0.5.5direct
crates.ioarbitrary1.4.2indirect
crates.iocc1.4.6indirect
crates.iocfg-if1.0.4indirect
crates.iodarling0.23.0indirect
crates.iodarling_core0.23.0indirect
crates.iodarling_macro0.23.0indirect
crates.iofind-msvc-tools0.1.12indirect
crates.iogetrandom0.4.3indirect
crates.ioident_case1.0.1indirect
crates.iojobserver0.1.35indirect
crates.iolibc0.2.189indirect
crates.iolibfuzzer-sys0.4.13indirect
crates.iopastey0.2.3indirect
crates.ior-efi6.0.0indirect
crates.ioshlex2.0.1indirect
crates.iostrsim0.11.1indirect
crates.iothiserror2.0.18indirect
crates.iothiserror-impl2.0.18indirect
crates.iounicode-ident1.0.24indirect
crates.iowincode-derive0.4.6indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 29 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 6 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

No known advisories affect the assessed dependencies.

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 statisticscrates.io.