Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 21:35 UTC

197g / static-alloc

Data structures like Rust `alloc` which reuse user allocated memory

RustApache-2.0★ 62 stars⑂ 11 forkssince Jul 2019View on GitHub ↗

197g/static-alloc holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Vitality (67/100) and lowest on AI Readiness (45/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Aurelia MolzerPersonal account
138 followers128 public repossince Sep 2013

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.iofillpoints to another repo — not scored0.1.13,46322406 days agono-stdfillextendembeddeddata-structures
crates.iounsizepoints to another repo — not scored1.1.0112,71341961 days agoembeddedno-std
crates.ioexit-stackpoints to another repo — not scored0.1.0312006 days agoembeddedmemory-managementno-std
crates.iosame-allocpoints to another repo — not scored1.0.0-alpha111990 days agoembeddeddata-structuresmemory-managementno-std
crates.ioalloc-traitspoints to another repo — not scored0.1.169,37422403 days agoembeddedmemory-managementno-std
crates.iostatic-alloc0.3.155,188191 day agono-stdmemory-managementembedded
crates.iowithout-allocpoints to another repo — not scored0.2.268,71431407 days agoembeddedno-stdmemory-management

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 1 days ago
2.8/36Commit cadence4/52 weeks with commits
13.8/18Commit volume33 commits in the last year
10/10OpenSSF Scorecard: Maintained29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year33
human_commit_share1
days_since_last_push1
active_weeks_last_year4
How it's scored
16.2/27Ships releases9 version tags (no GitHub releases)
36/36Release recencylatest release 1 days ago
12.6/27Release cadencea release every ~325.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count9
latest_release_tagv0.3.1
releases_from_tagsyes
days_since_latest_release1
mean_days_between_releases325.4
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?

54Moderate · 17% of overall
How it's scored
29/60Stars62 stars
8.3/25Forks11 forks
3.3/15Watchers5 watchers
Inputs used
forks11
stars62
watchers5
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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
63.2/80Monthly downloads55,188 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesstatic-alloc
dependents
ecosystemscrates
total_downloads1,010,877
monthly_downloads55,188
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?

62Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.5/22.5Commit distributiontop contributor authored 94% of commits
9.5/13.5Contributor breadth7 contributors
10/10OpenSSF Scorecard: Contributorsproject has 10 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.935
How it's scored
26.7/42Issue resolution64% of issues closed
29.6/30PR acceptance78/79 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 1/6 approved changesets -- score normalized to 1
Inputs used
merged_prs78
open_issues4
closed_issues7
prs_merged_7d4
prs_decided_7d4
prs_merged_30d5
prs_decided_30d5
issue_closed_ratio0.636
closed_unmerged_prs1
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
15.4/25Owner reach138 followers of 197g
25/25Track record128 public repos, account ~12 yr old
Inputs used
followers138
owner_typeUser
is_verified
owner_login197g
public_repos128
account_age_days4,719
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 crates
35/35Publish recencylatest publish 1 days ago
20/20Version history19 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesstatic-alloc
ecosystemscrates
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests5 out of 6 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/static-alloc
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_sitehttps://docs.rs/static-alloc
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

58Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2/2.5CI-Tests5 out of 6 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 1/6 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 10 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.7
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, 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
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages2
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the crates:static-alloc@0.3.1 runtime dependency closure — what installing the published package pulls in — 2 packages. 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.

45Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
17.6/40Legible commit history33 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.33
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml, alloc-traits/Cargo.toml, exit-stack/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingRust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency 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, alloc-traits/Cargo.toml, exit-stack/Cargo.toml, fill/Cargo.toml, same-alloc/Cargo.toml, static-alloc/Cargo.toml, unsize/Cargo.toml, without-alloc/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
53.9/55Manageable file sizes1/50 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes76,215
source_files_sampled50
oversized_source_files1

Key facts

62GitHub stars
7contributors
33commits, last 12 months
1days since last push
9releases
1bus factor
4open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • crates package 'fill' points at a different repository (https://github.com/HeroicKatora/static-alloc); excluded from ecosystem scoring
  • crates package 'unsize' points at a different repository (https://github.com/HeroicKatora/static-alloc); excluded from ecosystem scoring
  • crates package 'exit-stack' points at a different repository (https://github.com/HeroicKatora/static-alloc); excluded from ecosystem scoring
  • crates package 'same-alloc' points at a different repository (https://github.com/HeroicKatora/static-alloc); excluded from ecosystem scoring
  • crates package 'alloc-traits' points at a different repository (https://github.com/HeroicKatora/static-alloc); excluded from ecosystem scoring
  • crates package 'without-alloc' points at a different repository (https://github.com/HeroicKatora/static-alloc); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 11 ⇿
0Stars
11Forks
1Releases

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.

0246810121112019-102022-082025-07
Major 0Minor 0Patch 1

Each point covers 6 days.

OpenSSF Scorecard 4.7 / 10
4.7aggregate

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-28 21:35 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
8CI-Tests5 out of 6 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 1/6 approved changesets -- score normalized to 1
10Contributorsproject has 10 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained29 commit(s) and 0 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 5
RegistryPackageVersion constraintManifest
crates.iostatic-alloc0.3.0-prereleaseexit-stack/Cargo.toml
crates.ioalloc-traits0.1.0static-alloc/Cargo.toml
crates.ioportable-atomic1static-alloc/Cargo.toml
crates.ioalloc-traits0.1.0without-alloc/Cargo.toml
crates.iounsize1.1.0without-alloc/Cargo.toml
All dependencies 6

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

RegistryPackageVersionRelation
crates.ioalloc-traitsdirect
crates.ioportable-atomicdirect
crates.iostatic-allocdirect
crates.iounsizedirect
crates.ioautocfgindirect
crates.iopin-utilsindirect
Dependency advisories 0

Installing crates:static-alloc@0.3.1 pulls in 2 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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.