Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 08:07 UTC

Remade-With-Rust / rusty_alloc

rusty_alloc is a pure-Rust, memory safe alternative to mimalloc. Cross platform combability across x86-64 linux and windows, aarch64, wasm, and RSIC-V for ESP architecture.

RustCustom license★ 3 stars⑂ 1 forksince Aug 2026View on GitHub ↗
KindLibraryApplicationhow this is determined

Remade-With-Rust/rusty_alloc holds a health index of 67 out of 100, placing it in the Good band. It scores highest on AI Readiness (79/100) and lowest on Community & Adoption (34/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

Remade With RustOrganization
7 followers50 public repossince Jun 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iorusty_alloc2.2.04,339247 days agoallocatormallocmemorymimallocno-stddevelopment-toolsmemory-management
crates.iorusty_alloc-api2.2.04,295247 days agoallocatormallocmemorymimallocno-stddevelopment-toolsmemory-management

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
4.8/36Commit cadence7/52 weeks with commits
18/18Commit volume146 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year146
human_commit_share0.94
days_since_last_push1
active_weeks_last_year7

Release discipline

100Exceptional
How it's scored
27/27Ships releases27 releases published
36/36Release recencylatest release 7 days ago
27/27Release cadencea release every ~0.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count27
latest_release_tagrusty_alloc-api-v2.2.0
releases_from_tagsno
days_since_latest_release7
mean_days_between_releases0.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?

34At Risk · 17% of overall
How it's scored
4.9/60Stars3 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars3
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
52.5/80Monthly downloads8,634 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesrusty_alloc, rusty_alloc-api
dependents
ecosystemscrates
total_downloads25,902
monthly_downloads8,634
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?

53Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
5.7/22.5Commit distributiontop contributor authored 75% of commits
2.7/13.5Contributor breadth2 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.746
How it's scored
21/42Issue resolution50% of issues closed
28.9/30PR acceptance26/27 decided PRs merged
13/13Newcomer PR acceptance14/14 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/12 approved changesets -- score normalized to 0
Inputs used
merged_prs26
open_issues1
closed_issues1
prs_merged_7d1
prs_decided_7d1
prs_merged_30d14
prs_decided_30d14
issue_closed_ratio0.5
closed_unmerged_prs1
first_time_authors_30d1
first_time_prs_merged_30d14
first_time_prs_decided_30d14
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
6.5/25Owner reach7 followers of Remade-With-Rust
12.9/25Track record50 public repos, account ~0 yr old
Inputs used
followers7
owner_typeOrganization
is_verifiedno
owner_loginRemade-With-Rust
public_repos50
account_age_days89

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on crates
35/35Publish recencylatest publish 7 days ago
20/20Version history24 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesrusty_alloc, rusty_alloc-api
ecosystemscrates
any_deprecatedno
min_days_since_publish7

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter configCargo.toml ([workspace.lints]), crates/rusty_alloc/Cargo.toml ([lints]), crates/rusty_alloc_api/Cargo.toml ([lints]), crates/rusty_alloc_bench/Cargo.toml ([lints]), crates/rusty_alloc_ffi/Cargo.toml ([lints]), crates/rusty_alloc_override/Cargo.toml ([lints]), crates/rusty_alloc_wasm/Cargo.toml ([lints])
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://mata.network/remade-with-rust
10/10Repository description
10/10Topics18 topics
10/10Wiki
Inputs used
topicsallocator, remade-with-rust, rust, embedded, malloc, memory-allocator, memory-management, memory-safe, mimalloc, no-ffi, no-std, pure-rust, systems-programming, wasm, webassembly, embedded-systems, esp32, rsic-v
has_wikiyes
homepagehttps://mata.network/remade-with-rust
docs_sitehttps://mata.network/remade-with-rust
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

56Moderate · 16% of overall
How it's scored
1.5/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/12 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
5/5Fuzzingproject is fuzzed
2.2/2.5Licenselicense file detected
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
0/5Packagingno data
4/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file 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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
23/25Indirect dependencies free of known advisories1 affected: tracing-subscriber 0.3.19 (low)
39/40No advisories left outstanding1 advisory-carrying package(s) unaddressed past 90 days; oldest published 384 days ago
Inputs used
sourceosv
advisories2
affected_packages1
assessed_packages54
unassessed_packages0
affected_by_severitylow 1
direct_affected_packages0
Matched the crates:rusty_alloc@2.2.0 runtime dependency closure — what installing the published package pulls in — 54 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.

79Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://mata.network/llms.txt)
40/40Legible commit history87 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://mata.network/llms.txt
legible_history_share0.926
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml, bench/wasm-speed/Cargo.toml, crates/rusty_alloc/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format configCargo.toml ([workspace.lints]), crates/rusty_alloc/Cargo.toml ([lints]), crates/rusty_alloc_api/Cargo.toml ([lints]), crates/rusty_alloc_bench/Cargo.toml ([lints]), crates/rusty_alloc_ffi/Cargo.toml ([lints]), crates/rusty_alloc_override/Cargo.toml ([lints]), crates/rusty_alloc_wasm/Cargo.toml ([lints])
11/11Static type checkingRust (statically typed)
10/10Reproducible environmentlockfile
10/10Demonstrated agent practice63 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
8/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.63
toolchain_manifestsCargo.toml, bench/wasm-speed/Cargo.toml, crates/rusty_alloc/Cargo.toml, crates/rusty_alloc_api/Cargo.toml, crates/rusty_alloc_bench/Cargo.toml, crates/rusty_alloc_ffi/Cargo.toml, crates/rusty_alloc_override/Cargo.toml, crates/rusty_alloc_wasm/Cargo.toml, fuzz/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
50.8/55Manageable file sizes5/66 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes104,590
source_files_sampled66
oversized_source_files5

Key facts

3GitHub stars
2contributors
146commits, last 12 months
1days since last push
27releases
1bus factor
1open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'speedprobe' from its registry
  • Could not fetch crates package 'rusty_alloc-ffi' from its registry
  • Could not fetch crates package 'rusty_alloc-wasm' from its registry
  • Could not fetch crates package 'rusty_alloc-bench' from its registry
  • Could not fetch crates package 'rusty_alloc-override' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.6 / 10
4.6aggregate

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 08:07 UTC

2Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/12 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
9Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
n/aPackagingpackaging workflow not detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
crates.iorusty_alloc-apibench/wasm-speed/Cargo.toml
crates.iorusty_allocbench/wasm-speed/Cargo.toml
crates.iorusty_alloc2.2.0crates/rusty_alloc_api/Cargo.toml
crates.iorusty_alloccrates/rusty_alloc_bench/Cargo.toml
crates.iorusty_alloccrates/rusty_alloc_ffi/Cargo.toml
crates.iorusty_alloccrates/rusty_alloc_override/Cargo.toml
crates.iorusty_alloc-fficrates/rusty_alloc_override/Cargo.toml
crates.iorusty_alloccrates/rusty_alloc_wasm/Cargo.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 1

Installing crates:rusty_alloc@2.2.0 pulls in 54 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
tracing-subscriber0.3.19indirectlow20.3.20

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.