Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 19:55 UTC

lambdaclass / cairo-vm

cairo-vm is a Rust implementation of the Cairo VM. Cairo (CPU Algebraic Intermediate Representation) is a programming language for writing provable programs, where one party can prove to another that a certain computation was executed correctly without the need for this party to re-execute the same program.

Rust · CairoApache-2.0★ 0 stars⑂ 1 forksince Mar 2026forkView on GitHub ↗
KindNetwork serviceCommand-line toolLibraryhow this is determined

lambdaclass/cairo-vm holds a health index of 38 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (63/100) and lowest on Vitality (25/100). It was last updated 153 days ago. 3 contributors account for most of its recent work.

38
overall / 100
Weak

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.

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

Ownership

LambdaclassOrganization · verified domain
793 followers420 public repossince Jan 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iocairo-vm3.2.076,4756356 days agocairostarknetvm
crates.iofuzzerpoints to another repo — not scored0.0.2421414 days ago—

Metrics by category

Vitality

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

25At Risk · 21% of overall

Development activity

41Weak
How it's scored
9.9/36Push recency — last push 153 days ago
13.8/36Commit cadence — 20/52 weeks with commits
17.3/18Commit volume — 84 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year84
human_commit_share1
days_since_last_push153
active_weeks_last_year20

Release discipline

1Critical
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

29At Risk · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 0 stars
0/25Forks — 1 forks
0/15Watchers — 0 watchers
Inputs used
forks1
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

25At Risk
How it's scored
0/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_readmeno
has_licenseno
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno

Ecosystem adoption (downloads)

81Excellent
How it's scored
65.1/80Monthly downloads — 76,475 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagescairo-vm
dependents—
ecosystemscrates
total_downloads2,138,674
monthly_downloads76,475
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?

63Moderate · 23% of overall

Maintainer resilience (bus factor)

75Good
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
15.7/22.5Commit distribution — top contributor authored 30% of commits
13.5/13.5Contributor breadth — 100 contributors
10/10OpenSSF Scorecard: Contributors — project has 16 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled100
top_contributor_share0.3

Issue & PR responsiveness

1Critical
How it's scored
0/42Issue resolution — no issues or no data
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

96Exceptional
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
20.8/25Owner reach — 793 followers of lambdaclass
25/25Track record — 420 public repos, account ~12 yr old
Inputs used
followers793
owner_typeOrganization
is_verifiedyes
owner_loginlambdaclass
public_repos420
account_age_days4,606

Package maintenance

80Excellent
How it's scored
25/25Published & resolvable — 1 package(s) on crates
35/35Publish recency — latest publish 56 days ago
20/20Version history — 63 published versions
0/20Not deprecated — cairo-vm: deprecated/yanked on the registry
Inputs used
packagescairo-vm
ecosystemscrates
any_deprecatedyes
min_days_since_publish56

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall

Engineering practices

60Moderate
How it's scored
24/24CI workflows — 14 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage site — https://lambdaclass.github.io/cairo-vm
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://lambdaclass.github.io/cairo-vm
docs_sitehttps://lambdaclass.github.io/cairo-vm
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

29At Risk · 16% of overall

Security posture

29At Risk
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 16 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
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
0/7.5Vulnerabilities — 18 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate2.9
Excluded from scoring (no data or not applicable): CI-Tests, 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.

58Moderate · 4% of overall

Agent context & guidance

40Weak
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 97 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.97
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

63Moderate
How it's scored
18/18One-command bootstrap — Makefile, cairo1-run/Makefile, examples/custom_hint/Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
10/10Reproducible environment — lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile, cairo1-run/Makefile, examples/custom_hint/Makefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.01
toolchain_manifestsCargo.toml, cairo-vm-cli/Cargo.toml, cairo-vm-tracer/Cargo.toml, cairo1-run/Cargo.toml, examples/hyper_threading/Cargo.toml, fuzzer/Cargo.toml, hint_accountant/Cargo.toml, vm/Cargo.toml
dependency_bot_commit_share0

Code legibility for models

98Exceptional
How it's scored
45/45Type-checkable code — Rust (statically typed)
52.6/55Manageable file sizes — 7/163 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes215,238
source_files_sampled163
oversized_source_files7

Machine-readable interfaces

40Weak
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—
interfaces_expected_ofnetwork-service

Key facts

0GitHub stars
100contributors
84commits, last 12 months
153days since last push
0releases
3bus factor
0open issues
crates.io, PyPIpackage ecosystems

Data collection warnings

  • Community profile unavailable
  • crates package 'fuzzer' points at a different repository (https://github.com/Eveheeero/debugger); excluded from ecosystem scoring
  • Could not fetch crates package 'cairo1-run' from its registry
  • Could not fetch crates package 'cairo-vm-cli' from its registry
  • Could not fetch crates package 'cairo-vm-tracer' from its registry
  • Could not fetch crates package 'hint_accountant' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 2.9 / 10
2.9aggregate

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-09 19:55 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 16 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities18 existing vulnerabilities detected
Direct dependencies 68
RegistryPackageVersion constraintManifest
crates.iocairo-vm—cairo-vm-cli/Cargo.toml
crates.iocairo-vm-tracer—cairo-vm-cli/Cargo.toml
crates.ioclap4.3.10cairo-vm-cli/Cargo.toml
crates.iomimalloc0.1.37cairo-vm-cli/Cargo.toml
crates.iothiserror—cairo-vm-cli/Cargo.toml
crates.iocairo-vm—cairo-vm-tracer/Cargo.toml
crates.iothiserror—cairo-vm-tracer/Cargo.toml
crates.ionum-bigint—cairo-vm-tracer/Cargo.toml
crates.ionum-traits—cairo-vm-tracer/Cargo.toml
crates.ioaxum0.6.18cairo-vm-tracer/Cargo.toml
crates.iotokio1.28.2cairo-vm-tracer/Cargo.toml
crates.ioserde—cairo-vm-tracer/Cargo.toml
crates.iotower-http0.4.0cairo-vm-tracer/Cargo.toml
crates.iotracing0.1.37cairo-vm-tracer/Cargo.toml
crates.iotracing-subscriber0.3.17cairo-vm-tracer/Cargo.toml
crates.ioinclude_dir0.7.3cairo-vm-tracer/Cargo.toml
crates.iomime_guess2.0.4cairo-vm-tracer/Cargo.toml
crates.iocairo-vm—cairo1-run/Cargo.toml
crates.ioserde_json—cairo1-run/Cargo.toml
crates.iocairo-lang-sierra-type-size2.12.0-dev.0cairo1-run/Cargo.toml
crates.iocairo-lang-sierra-to-casm—cairo1-run/Cargo.toml
crates.iocairo-lang-compiler—cairo1-run/Cargo.toml
crates.iocairo-lang-sierra—cairo1-run/Cargo.toml
crates.iocairo-lang-utils—cairo1-run/Cargo.toml
crates.iocairo-lang-casm—cairo1-run/Cargo.toml
crates.ioitertools0.11.0cairo1-run/Cargo.toml
crates.ioclap4.3.10cairo1-run/Cargo.toml
crates.iothiserror—cairo1-run/Cargo.toml
crates.ioassert_matches1.5.0cairo1-run/Cargo.toml
crates.iorstest0.17.0cairo1-run/Cargo.toml
crates.ionum-traits0.2cairo1-run/Cargo.toml
crates.ionum-bigint—cairo1-run/Cargo.toml
crates.ioarbitrary1.3.0fuzzer/Cargo.toml
crates.iocairo-vm—fuzzer/Cargo.toml
crates.iohonggfuzz=0.5.58fuzzer/Cargo.toml
crates.ioserde1.0.180fuzzer/Cargo.toml
crates.ioserde_json1.0.104fuzzer/Cargo.toml
crates.iocairo-vm—hint_accountant/Cargo.toml
crates.ioserde—hint_accountant/Cargo.toml
crates.ioserde_json1.0hint_accountant/Cargo.toml
crates.iozip0.6.6vm/Cargo.toml
crates.ionum-bigint—vm/Cargo.toml
crates.iorand—vm/Cargo.toml
crates.ionum-traits—vm/Cargo.toml
crates.ionum-integer—vm/Cargo.toml
crates.ioserde—vm/Cargo.toml
crates.ioserde_json—vm/Cargo.toml
crates.iostarknet-crypto—vm/Cargo.toml
crates.iosha3—vm/Cargo.toml
crates.iotracing—vm/Cargo.toml
crates.ioindoc—vm/Cargo.toml
crates.iolazy_static—vm/Cargo.toml
crates.ionom—vm/Cargo.toml
crates.iosha2—vm/Cargo.toml
crates.iogeneric-array—vm/Cargo.toml
crates.iokeccak—vm/Cargo.toml
crates.ioanyhow—vm/Cargo.toml
crates.iothiserror—vm/Cargo.toml
crates.iostarknet-types-core0.2.4vm/Cargo.toml
crates.iorust_decimal1.35.0vm/Cargo.toml
crates.ionum-prime0.4.3vm/Cargo.toml
crates.iobitvec—vm/Cargo.toml
crates.iocairo-lang-starknet-classes—vm/Cargo.toml
crates.iocairo-lang-casm—vm/Cargo.toml
crates.ioark-ff—vm/Cargo.toml
crates.ioark-std—vm/Cargo.toml
crates.ioarbitrary—vm/Cargo.toml
crates.ioclap4.3.10vm/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

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with lambdaclass/cairo-vm. Read them side by side →

34software-mansion/protostarProtostar is a toolchain for developing and testing Starknet contractsAt Risk98starkware-libs/cairoCairo is the first Turing-complete language for creating provable programs for general computation.Exceptional95foundry-rs/starknet-foundryBlazing fast toolkit for developing Starknet contracts.Exceptional92starkware-libs/cairo_nativeA compiler to convert Cairo's intermediate representation "Sierra" code to MLIR.Excellent91software-mansion/scarbThe Cairo package managerExcellent73software-mansion/cairo-profilerProfiler for Cairo programming language & StarknetGood

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 statistics — crates.io.