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

zip-rs / zip2

Zip implementation in Rust

RustMIT★ 341 stars⑂ 111 forkssince Apr 2023View on GitHub ↗

zip-rs/zip2 holds a health index of 91 out of 100, placing it in the Excellent band. It scores highest on Vitality (96/100) and lowest on Sustainability & Governance (62/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

zip-rsOrganization
9 followers2 public repossince Sep 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iozip8.6.019,700,03513089 days agocompressionziparchiveparser-implementationsfilesystem

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
29.1/36Commit cadence — 42/52 weeks with commits
18/18Commit volume — 442 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year442
human_commit_share0.52
days_since_last_push0
active_weeks_last_year42

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 59 releases published
36/36Release recency — latest release 89 days ago
27/27Release cadence — a release every ~9.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count59
latest_release_tagv9.0.0-pre2
releases_from_tagsno
days_since_latest_release89
mean_days_between_releases9.3
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?

82Excellent · 17% of overall
How it's scored
41.1/60Stars — 341 stars
17/25Forks — 111 forks
2.7/15Watchers — 4 watchers
Inputs used
forks111
stars341
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io, www.bestpractices.dev
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 19,700,035 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageszip
dependents
ecosystemscrates
total_downloads233,581,300
monthly_downloads19,700,035
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?

62Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.3/22.5Commit distribution — top contributor authored 63% of commits
13.5/13.5Contributor breadth — 94 contributors
10/10OpenSSF Scorecard: Contributors — project has 38 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled94
top_contributor_share0.631
How it's scored
30.7/42Issue resolution — 73% of issues closed
23.6/30PR acceptance — 566/719 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-Review — Found 2/9 approved changesets -- score normalized to 2
Inputs used
merged_prs566
open_issues45
closed_issues123
prs_merged_7d1
prs_decided_7d1
prs_merged_30d4
prs_decided_30d6
issue_closed_ratio0.732
closed_unmerged_prs153
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
7.2/25Owner reach — 9 followers of zip-rs
15.3/25Track record — 2 public repos, account ~5 yr old
Inputs used
followers9
owner_typeOrganization
is_verified
owner_loginzip-rs
public_repos2
account_age_days2,155

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 9 workflow(s)
24/24Tests present
16/16Linter config
9.6/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_configyes

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

72Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0.5/2.5CII-Best-Practices — badge detected: InProgress
1.5/7.5Code-Review — Found 2/9 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 38 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file 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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7.2
Excluded from scoring (no data or not applicable): packaging, 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.

67Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 52 of 52 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrap — Cargo.toml, fuzz/Cargo.toml, fuzz/read/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
10/10Demonstrated agent practice — 21 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 47 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.21
toolchain_manifestsCargo.toml, fuzz/Cargo.toml, fuzz/read/Cargo.toml, fuzz/write/Cargo.toml
dependency_bot_commit_share0.47
How it's scored
45/45Type-checkable code — Rust (statically typed)
54.3/55Manageable file sizes — 1/79 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes191,519
source_files_sampled79
oversized_source_files1
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

341GitHub stars
94contributors
442commits, last 12 months
0days since last push
59releases
1bus factor
45open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 111 ⇿
0Stars
111Forks
59Releases

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.

02040608010012011032024-042025-062026-08
Major 7Minor 25Patch 24

Each point covers 3 days.

OpenSSF Scorecard 7.2 / 10
7.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-08-08 20:07 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
2CII-Best-Practicesbadge detected: InProgress
2Code-ReviewFound 2/9 approved changesets -- score normalized to 2
10Contributorsproject has 38 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 22
RegistryPackageVersion constraintManifest
crates.ioarbitrary1.4Cargo.toml
crates.ioaes0.9Cargo.toml
crates.iobzip20.6Cargo.toml
crates.iochrono^0.4.27Cargo.toml
crates.ioconstant_time_eq0.4Cargo.toml
crates.iocrc32fast1.5Cargo.toml
crates.ioflate21.1Cargo.toml
crates.iohmac0.13Cargo.toml
crates.ioindexmap2Cargo.toml
crates.iojiff^0.2.4Cargo.toml
crates.iomemchr2.7Cargo.toml
crates.iont-time0.13Cargo.toml
crates.ioppmd-rust1.4Cargo.toml
crates.iopbkdf20.13Cargo.toml
crates.iosha10.11Cargo.toml
crates.iozeroize1.8Cargo.toml
crates.iozstd^0.13.3Cargo.toml
crates.iozopfli^0.8.3Cargo.toml
crates.iodeflate64^0.1.10Cargo.toml
crates.iolzma-rust2^0.18.0Cargo.toml
crates.iobitstream-io4.9Cargo.toml
crates.iotyped-path0.12Cargo.toml
All dependencies 31

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

RegistryPackageVersionRelation
crates.ioaesdirect
crates.ioarbitrarydirect
crates.iobitstream-iodirect
crates.iobzip2direct
crates.iochronodirect
crates.ioconstant_time_eqdirect
crates.iocrc32fastdirect
crates.iodeflate64direct
crates.ioflate2direct
crates.iohmacdirect
crates.ioindexmapdirect
crates.iojiffdirect
crates.iolzma-rust2direct
crates.iomemchrdirect
crates.iont-timedirect
crates.iopbkdf2direct
crates.ioppmd-rustdirect
crates.iosha1direct
crates.iotyped-pathdirect
crates.iozeroizedirect
crates.iozopflidirect
crates.iozstddirect
crates.iobencherindirect
crates.ioclapindirect
crates.iogetrandomindirect
crates.iorayonindirect
crates.ioreplace_withindirect
crates.iotempfileindirect
crates.iotimeindirect
crates.iowalkdirindirect
crates.iowasm-bindgen-testindirect
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

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