Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 20:11 UTC

broxus / tycho-vm

RustApache-2.0★ 4 stars⑂ 1 forksince Sep 2023View on GitHub ↗
KindLibraryhow this is determined

broxus/tycho-vm holds a health index of 32 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (70/100) and lowest on Engineering Quality (28/100). It was last updated 47 days ago. A single contributor accounts for most of its recent work.

32
overall / 100
At Risk

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.

32
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 45 is calibrated to 42 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 75% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

BroxusOrganization · verified domain
106 followers220 public repossince Sep 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
crates.iotycho-vm0.3.72,1401047 days ago
crates.iotycho-disasm0.3.728847 days ago
crates.iotycho-vm-proc0.3.32,1136214 days ago
crates.iotycho-executor0.3.71,9971047 days ago

Metrics by category

Vitality

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

50Moderate · 21% of overall

Development activity

50Moderate
How it's scored
18/36Push recency — last push 47 days ago
13.8/36Commit cadence — 20/52 weeks with commits
14.5/18Commit volume — 40 commits in the last year
4/10OpenSSF Scorecard: Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year40
human_commit_share1
days_since_last_push47
active_weeks_last_year20

Release discipline

50Moderate
How it's scored
16.2/27Ships releases — 1 version tags (no GitHub releases)
16.2/36Release recency — latest release 349 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv0.3.0
releases_from_tagsyes
days_since_latest_release349
mean_days_between_releases—
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?

38Weak · 17% of overall

Popularity & adoption

13Critical
How it's scored
7.7/60Stars — 4 stars
0/25Forks — 1 forks
5.3/15Watchers — 10 watchers
Inputs used
forks1
stars4
watchers10
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

63Moderate
How it's scored
50.6/80Monthly downloads — 6,278 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagestycho-vm, tycho-disasm, tycho-vm-proc, tycho-executor
dependents—
ecosystemscrates
total_downloads61,115
monthly_downloads6,278
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?

70Good · 23% of overall

Maintainer resilience (bus factor)

32At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.8/22.5Commit distribution — top contributor authored 74% of commits
6.8/13.5Contributor breadth — 5 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.742

Issue & PR responsiveness

70Good
How it's scored
33.6/42Issue resolution — 80% of issues closed
25.7/30PR acceptance — 18/21 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 4/27 approved changesets -- score normalized to 1
Inputs used
merged_prs18
open_issues1
closed_issues4
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.8
closed_unmerged_prs3
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.

Ownership & stewardship

90Excellent
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
14.6/25Owner reach — 106 followers of broxus
25/25Track record — 220 public repos, account ~6 yr old
Inputs used
followers106
owner_typeOrganization
is_verifiedyes
owner_loginbroxus
public_repos220
account_age_days2,551

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 4 package(s) on crates
35/35Publish recency — latest publish 47 days ago
20/20Version history — 10 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagestycho-vm, tycho-disasm, tycho-vm-proc, tycho-executor
ecosystemscrates
any_deprecatedno
min_days_since_publish47

Engineering Quality

Are baseline engineering and documentation practices in place?

28At Risk · 19% of overall

Engineering practices

16Critical
How it's scored
0/24CI workflows
0/24Tests present
16/16Linter config — rustfmt.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 4 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

45Weak
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/tycho-vm
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_sitehttps://docs.rs/tycho-vm
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

31At Risk · 16% of overall

Security posture

31At Risk
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 4/27 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 4 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file detected
3/7.5Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.1
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier75
security_posture_after_multiplier31
security_posture_before_jurisdiction41
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 75% multiplier and gives Security posture an At risk ceiling of 34.

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.

39Weak · 4% of overall

Agent context & guidance

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

Verify loop (build / test / typecheck)

38Weak
How it's scored
12.6/18One-command bootstrap — Cargo.toml, disasm/Cargo.toml, executor/Cargo.toml (toolchain convention, no task runner)
0/22Automated tests
11/11Lint / format config — rustfmt.toml
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml, disasm/Cargo.toml, executor/Cargo.toml, fuzz/Cargo.toml, vm-proc/Cargo.toml, vm/Cargo.toml
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

96Exceptional
How it's scored
45/45Type-checkable code — Rust (statically typed)
50.8/55Manageable file sizes — 4/53 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes117,108
source_files_sampled53
oversized_source_files4

Key facts

4GitHub stars
5contributors
40commits, last 12 months
47days since last push
1releases
1bus factor
1open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 4.1 / 10
4.1aggregate

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-14 20:11 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 4/27 approved changesets -- score normalized to 1
10Contributorsproject has 4 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 34
RegistryPackageVersion constraintManifest
crates.ioahash—disasm/Cargo.toml
crates.ioanyhow—disasm/Cargo.toml
crates.ionum-bigint—disasm/Cargo.toml
crates.ioserde—disasm/Cargo.toml
crates.iosmol_str—disasm/Cargo.toml
crates.iothiserror—disasm/Cargo.toml
crates.iotycho-types—disasm/Cargo.toml
crates.iotycho-vm—disasm/Cargo.toml
crates.ioahash—executor/Cargo.toml
crates.ioanyhow—executor/Cargo.toml
crates.ionum-bigint—executor/Cargo.toml
crates.iothiserror—executor/Cargo.toml
crates.iotycho-types—executor/Cargo.toml
crates.iotycho-vm—executor/Cargo.toml
crates.ioquote—vm-proc/Cargo.toml
crates.iosyn—vm-proc/Cargo.toml
crates.iodarling—vm-proc/Cargo.toml
crates.ioproc-macro2—vm-proc/Cargo.toml
crates.ioahash—vm/Cargo.toml
crates.ioanyhow—vm/Cargo.toml
crates.ioarbitrary—vm/Cargo.toml
crates.iobitflags—vm/Cargo.toml
crates.ioblake2—vm/Cargo.toml
crates.iodyn-clone—vm/Cargo.toml
crates.ionum-bigint—vm/Cargo.toml
crates.ionum-integer—vm/Cargo.toml
crates.ionum-traits—vm/Cargo.toml
crates.iosha2—vm/Cargo.toml
crates.iothiserror—vm/Cargo.toml
crates.iotl-proto—vm/Cargo.toml
crates.iotracing—vm/Cargo.toml
crates.iotycho-crypto—vm/Cargo.toml
crates.iotycho-types—vm/Cargo.toml
crates.iotycho-vm-proc—vm/Cargo.toml
All dependencies 0

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

RegistryPackageVersionRelation
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies to assess

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 broxus/tycho-vm. Read them side by side →

100scalar/scalarScalar is an open-source API platform:　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　🌐 Modern REST API Client　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　📖 Beautiful API References　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　✨ 1st-Class OpenAPI/Swagger SupportExceptional100envoyproxy/envoyCloud-native high-performance edge/middle/service proxyExceptional100risingwavelabs/risingwaveEvent streaming platform for agentic AI. Continuously ingest, transform, and serve event streams in real time, at scale.Exceptional100wandb/wandbThe AI developer platform. Use Weights & Biases to train and fine-tune models, and manage models from experimentation to production.Exceptional100microsoft/onnxruntimeONNX Runtime: cross-platform, high performance ML inferencing and training acceleratorExceptional99ai-dynamo/dynamoA Datacenter Scale Distributed Inference Serving FrameworkExceptional

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.