Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 13:12 UTC

rust-vmm / vfio

RustNo license detected★ 43 stars⑂ 48 forkssince Dec 2021View on GitHub ↗

rust-vmm/vfio holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (85/100) and lowest on Engineering Quality (48/100). It was last updated 11 days ago. 4 contributors account for most of its recent work.

80
overall / 100
Excellent

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.

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

Ownership

rust-vmmOrganization
1,026 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 publishTags
crates.iovfio_user0.1.527,452624 days ago
crates.iovfio-ioctls0.8.171,3981124 days agovfio
crates.iovfio-bindings0.6.2140,7588171 days agovfio

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
28.8/36Push recencylast push 11 days ago
13.2/36Commit cadence19/52 weeks with commits
15/18Commit volume46 commits in the last year
10/10OpenSSF Scorecard: Maintained13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year46
human_commit_share0.92
days_since_last_push11
active_weeks_last_year19
How it's scored
27/27Ships releases13 releases published
36/36Release recencylatest release 53 days ago
19.8/27Release cadencea release every ~48.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count13
latest_release_tagvfio-ioctls-v0.8.0
releases_from_tagsno
days_since_latest_release53
mean_days_between_releases48.7
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?

52Moderate · 17% of overall
How it's scored
26.3/60Stars43 stars
13.9/25Forks48 forks
6.2/15Watchers14 watchers
Inputs used
forks48
stars43
watchers14
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
How it's scored
22.5/22.5README
0/22.5Licenseno 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
71.7/80Monthly downloads239,608 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesvfio_user, vfio-ioctls, vfio-bindings
dependents
ecosystemscrates
total_downloads2,160,941
monthly_downloads239,608
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?

85Excellent · 23% of overall
How it's scored
43.2/54Bus factor4 contributor(s) cover half of all commits
18.8/22.5Commit distributiontop contributor authored 16% of commits
13.5/13.5Contributor breadth29 contributors
10/10OpenSSF Scorecard: Contributorsproject has 15 contributing companies or organizations
Inputs used
bus_factor4
contributors_sampled29
top_contributor_share0.165
How it's scored
34.6/42Issue resolution82% of issues closed
20.7/30PR acceptance102/148 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs102
open_issues3
closed_issues14
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.824
closed_unmerged_prs46
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.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
21.7/25Owner reach1,026 followers of rust-vmm
23.2/25Track record34 public repos, account ~7 yr old
Inputs used
followers1,026
owner_typeOrganization
is_verifiedno
owner_loginrust-vmm
public_repos34
account_age_days2,822

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable3 package(s) on crates
35/35Publish recencylatest publish 24 days ago
20/20Version history11 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesvfio_user, vfio-ioctls, vfio-bindings
ecosystemscrates
any_deprecatedno
min_days_since_publish24

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests18 out of 18 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://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?

74Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests18 out of 18 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 15 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
7.5/7.5Maintained13 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
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_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.8
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_packages33
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:vfio_user@0.1.5 runtime dependency closure — what installing the published package pulls in — 33 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.

53Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history83 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.902
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml, vfio-bindings/Cargo.toml, vfio-ioctls/Cargo.toml (toolchain convention, no task runner)
0/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
8/8Automated maintenance8 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml, vfio-bindings/Cargo.toml, vfio-ioctls/Cargo.toml, vfio-user/Cargo.toml
dependency_bot_commit_share0.08
How it's scored
45/45Type-checkable codeRust (statically typed)
45/55Manageable file sizes2/11 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes108,678
source_files_sampled11
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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

43GitHub stars
29contributors
46commits, last 12 months
11days since last push
13releases
4bus factor
3open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-06-08: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 43 stars today.
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 38 ★ / 48 ⇿
38Stars
48Forks
13Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-06-08. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

01020304050384732021-122024-042026-08
Major 0Minor 0Patch 1

Each point covers 5 days.

OpenSSF Scorecard 6.8 / 10
6.8aggregate

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-12 13:12 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
10CI-Tests18 out of 18 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 15 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained13 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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 25
RegistryPackageVersion constraintManifest
crates.iovmm-sys-utilvfio-bindings/Cargo.toml
crates.iobyteorder1.2.1vfio-ioctls/Cargo.toml
crates.iolibc0.2.39vfio-ioctls/Cargo.toml
crates.iolog0.4vfio-ioctls/Cargo.toml
crates.iokvm-bindings0.14.0vfio-ioctls/Cargo.toml
crates.iokvm-ioctls0.25.0vfio-ioctls/Cargo.toml
crates.iothiserrorvfio-ioctls/Cargo.toml
crates.iovfio-bindings=0.6.2vfio-ioctls/Cargo.toml
crates.iovm-memory0.18vfio-ioctls/Cargo.toml
crates.iovmm-sys-utilvfio-ioctls/Cargo.toml
crates.iomshv-bindings0.7.0vfio-ioctls/Cargo.toml
crates.iomshv-ioctls0.7.0vfio-ioctls/Cargo.toml
crates.ioiommufd-bindings0.1.0vfio-ioctls/Cargo.toml
crates.ioiommufd-ioctls0.2.0vfio-ioctls/Cargo.toml
crates.iobitflags2.9.4vfio-user/Cargo.toml
crates.ioenumn0.1.14vfio-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.iothiserrorvfio-user/Cargo.toml
crates.iovfio-bindings=0.6.2vfio-user/Cargo.toml
crates.iovm-memory>= 0.16.0, < 0.19vfio-user/Cargo.toml
crates.iovmm-sys-utilvfio-user/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 0

Installing crates:vfio_user@0.1.5 pulls in 33 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.