Public record
Software health reportschema 0.17.0 · metrics 2.10.0 · 2026-07-21 07:09 UTC

rust-vmm / vfio-user

RustNo license detected★ 7 stars⑂ 11 forkssince Jan 2023archivedView on GitHub ↗
KindLibraryhow this is determined

rust-vmm/vfio-user holds a health index of 14 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (84/100) and lowest on Vitality (1/100). The repository is archived, so no further maintenance is expected.

14
overall / 100
Critical

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.

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

Ownership

rust-vmmOrganization
1,001 followers34 public repossince Dec 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
crates.iovfio_user0.1.425,56550 days ago

Metrics by category

Vitality

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

1Critical · 21% of overall

Development activity

1Critical
How it's scored
0/36Push recency — last push 426 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — project is archived
Inputs used
commits_last_year0
human_commit_share—
days_since_last_push426
active_weeks_last_year0

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?

40Weak · 17% of overall

Popularity & adoption

26At Risk
How it's scored
12.6/60Stars — 7 stars
8.3/25Forks — 11 forks
5/15Watchers — 9 watchers
Inputs used
forks11
stars7
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold

Community health

32At Risk
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes

Ecosystem adoption (downloads)

74Good
How it's scored
58.8/80Monthly downloads — 25,565 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesvfio_user
dependents—
ecosystemscrates
total_downloads191,071
monthly_downloads25,565
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?

84Excellent · 23% of overall

Maintainer resilience (bus factor)

61Moderate
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.2/22.5Commit distribution — top contributor authored 46% of commits
13.5/13.5Contributor breadth — 12 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled12
top_contributor_share0.457

Issue & PR responsiveness

88Excellent
How it's scored
42/42Issue resolution — 100% of issues closed
19.2/30PR acceptance — 23/36 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs23
open_issues0
closed_issues3
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio1
closed_unmerged_prs13
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

94Exceptional
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
21.6/25Owner reach — 1,001 followers of rust-vmm
23.2/25Track record — 34 public repos, account ~7 yr old
Inputs used
followers1,001
owner_typeOrganization
is_verified—
owner_loginrust-vmm
public_repos34
account_age_days2,769
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on crates
35/35Publish recency — latest publish 0 days ago
20/20Version history — 5 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesvfio_user
ecosystemscrates
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

23At Risk · 19% of overall

Engineering practices

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

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/vfio_user
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://docs.rs/vfio_user
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

54Moderate · 16% of overall

Security posture

54Moderate
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 19 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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 6 contributing companies or organizations
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
0/7.5Maintained — project is archived
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file 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_aggregate5.4
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

36Weak · 4% of overall

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

Verify loop (build / test / typecheck)

15Critical
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no data
0/8Automated maintenance — no data
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share—
toolchain_manifests—
dependency_bot_commit_share—
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — Rust (statically typed)
55/55Manageable file sizes — 0/3 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes42,752
source_files_sampled3
oversized_source_files0

Machine-readable interfaces

100Exceptional
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

7GitHub stars
12contributors
0commits, last 12 months
426days since last push
0releases
2bus factor
0open issues
crates.iopackage ecosystems

Data collection warnings

  • deps.dev does not index crates:vfio_user@0.1.4; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 7 ★ / 0 ⇿
7Stars

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.

1234567712023-022024-102026-06

Each point covers 3 days.

OpenSSF Scorecard 5.4 / 10
5.4aggregate

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-07-21 07:09 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 19 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 6 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
0Maintainedproject is archived
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
crates.iobitflags2.9.0vfio-user/Cargo.toml
crates.iolibc0.2.139vfio-user/Cargo.toml
crates.iolog0.4.17vfio-user/Cargo.toml
crates.ioserde1.0.151vfio-user/Cargo.toml
crates.ioserde_derive1.0.149vfio-user/Cargo.toml
crates.ioserde_json1.0.93vfio-user/Cargo.toml
crates.iothiserror2.0.12vfio-user/Cargo.toml
crates.iovfio-bindings0.4.0vfio-user/Cargo.toml
crates.iovm-memory0.16.0vfio-user/Cargo.toml
crates.iovmm-sys-util0.13.0vfio-user/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 rust-vmm/vfio-user. Read them side by side →

100envoyproxy/envoyCloud-native high-performance edge/middle/service proxyExceptional100wandb/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 acceleratorExceptional100risingwavelabs/risingwaveEvent streaming platform for agentic AI. Continuously ingest, transform, and serve event streams in real time, at scale.Exceptional99rust-lang/rustEmpowering everyone to build reliable and efficient software.Exceptional99modelcontextprotocol/rust-sdkThe official Rust SDK for the Model Context ProtocolExceptional

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.17.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — crates.io.