Public record
Software health reportschema 0.30.0 · metrics 2.5.0 · 2026-08-03 04:43 UTC

hasenbanck / sevenz-rust2

Rust native 7z compressor / decompressor

RustApache-2.0★ 106 stars⑂ 26 forkssince Feb 2025View on GitHub ↗

hasenbanck/sevenz-rust2 holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Vitality (83/100) and lowest on Community & Adoption (47/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Nils HasenbanckPersonal account
48 followers41 public repossince Apr 2015

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iosevenz-rust2points to another repo — not scored0.21.4115,171351 day ago7z7zipdecompresssevenz

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 recency — last push 1 days ago
16.6/36Commit cadence — 24/52 weeks with commits
16.2/18Commit volume — 62 commits in the last year
10/10OpenSSF Scorecard: Maintained — 10 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year62
human_commit_share0.82
days_since_last_push1
active_weeks_last_year24
How it's scored
16.2/27Ships releases — 32 version tags (no GitHub releases)
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~30.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count32
latest_release_tagv0.21.4
releases_from_tagsyes
days_since_latest_release1
mean_days_between_releases30.7
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?

47Weak · 17% of overall
How it's scored
32.8/60Stars — 106 stars
11.7/25Forks — 26 forks
0/15Watchers — 1 watchers
Inputs used
forks26
stars106
watchers1
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_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

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

50Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.2/22.5Commit distribution — top contributor authored 72% of commits
13.5/13.5Contributor breadth — 17 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled17
top_contributor_share0.725
How it's scored
34.1/42Issue resolution — 81% of issues closed
22.3/30PR acceptance — 70/94 decided PRs merged
4.3/13Newcomer PR acceptance — 1/3 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 4/13 approved changesets -- score normalized to 3
Inputs used
merged_prs70
open_issues6
closed_issues26
prs_merged_7d1
prs_decided_7d1
prs_merged_30d3
prs_decided_30d5
issue_closed_ratio0.812
closed_unmerged_prs24
first_time_authors_30d3
first_time_prs_merged_30d1
first_time_prs_decided_30d3
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
12.2/25Owner reach — 48 followers of hasenbanck
23.8/25Track record — 41 public repos, account ~11 yr old
Inputs used
followers48
owner_typeUser
is_verified
owner_loginhasenbanck
public_repos41
account_age_days4,119
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

60Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 22 out of 23 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

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?

50Moderate · 16% of overall
How it's scored
6/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.2/2.5CI-Tests — 22 out of 23 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 4/13 approved changesets -- score normalized to 3
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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 — 10 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5
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.

48Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
16.9/40Legible commit history — 26 of 82 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.317
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrap — Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 18 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml
dependency_bot_commit_share0.18
How it's scored
45/45Type-checkable code — Rust (statically typed)
53.6/55Manageable file sizes — 1/38 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes70,239
source_files_sampled38
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — examples, sample
Inputs used
example_dirsexamples, sample
has_mcp_signalno
api_schema_files

Key facts

106GitHub stars
17contributors
62commits, last 12 months
1days since last push
32releases
1bus factor
6open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • crates package 'sevenz-rust2' points at a different repository (https://github.com/hasenbanck/sevenz-rust); excluded from ecosystem scoring
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 26 ⇿
0Stars
26Forks
24Releases

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.

0510152025302612025-032025-112026-07
Major 0Minor 7Patch 17

Each point covers 2 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-03 04:43 UTC

8Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
9CI-Tests22 out of 23 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 4/13 approved changesets -- score normalized to 3
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained10 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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 13
RegistryPackageVersion constraintManifest
crates.ioaes0.9Cargo.toml
crates.iobrotli>= 7, < 9Cargo.toml
crates.iobzip20.6Cargo.toml
crates.iocbc0.2Cargo.toml
crates.iocrc32fast1Cargo.toml
crates.ioflate21Cargo.toml
crates.iogetrandom0.4Cargo.toml
crates.iolzma-rust20.18Cargo.toml
crates.ioppmd-rust1Cargo.toml
crates.iolz4_flex0.14Cargo.toml
crates.iont-time0.15Cargo.toml
crates.iosha20.11Cargo.toml
crates.iozstd0.13Cargo.toml
All dependencies 17

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

RegistryPackageVersionRelation
crates.ioaesdirect
crates.iobrotlidirect
crates.iobzip2direct
crates.iocbcdirect
crates.iocrc32fastdirect
crates.ioflate2direct
crates.iogetrandomdirect
crates.iolz4_flexdirect
crates.iolzma-rust2direct
crates.iont-timedirect
crates.ioppmd-rustdirect
crates.iosha2direct
crates.iozstddirect
crates.iojs-sysindirect
crates.iorandindirect
crates.iotempfileindirect
crates.iowasm-bindgenindirect
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.30.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticscrates.io.