Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-26 02:29 UTC

microsoft / igvm

RustMIT★ 155 stars⑂ 42 forkssince Aug 2023View on GitHub ↗

microsoft/igvm holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (84/100) and lowest on Vitality (62/100). It was last updated 1 day ago. 3 contributors account for most of its recent work.

81
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.

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

Ownership

MicrosoftOrganization · verified domain
130,479 followers8,310 public repossince Dec 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.ioigvm0.5.038,932191 day agovirtualizationparser-implementations
crates.ioigvm_defs0.5.039,161191 day agovirtualizationno-std

Metrics by category

Vitality

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

62Moderate · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
10.4/36Commit cadence — 15/52 weeks with commits
12.9/18Commit volume — 26 commits in the last year
9/10OpenSSF Scorecard: Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year26
human_commit_share0.99
days_since_last_push1
active_weeks_last_year15
How it's scored
27/27Ships releases — 3 releases published
7.2/36Release recency — latest release 410 days ago
12.6/27Release cadence — a release every ~254.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tagigvm-v0.4.0
releases_from_tagsno
days_since_latest_release410
mean_days_between_releases254.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?

65Good · 17% of overall
How it's scored
35.5/60Stars — 155 stars
13.4/25Forks — 42 forks
5.3/15Watchers — 10 watchers
Inputs used
forks42
stars155
watchers10
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
65.2/80Monthly downloads — 78,093 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesigvm, igvm_defs
dependents—
ecosystemscrates
total_downloads1,120,701
monthly_downloads78,093
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
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
14.8/22.5Commit distribution — top contributor authored 34% of commits
13.5/13.5Contributor breadth — 25 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor3
contributors_sampled25
top_contributor_share0.344
How it's scored
19.1/42Issue resolution — 46% of issues closed
29.7/30PR acceptance — 97/98 decided PRs merged
6.5/13Newcomer PR acceptance — 1/2 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs97
open_issues18
closed_issues15
prs_merged_7d1
prs_decided_7d2
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio0.455
closed_unmerged_prs1
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 130,479 followers of microsoft
25/25Track record — 8,310 public repos, account ~12 yr old
Inputs used
followers130,479
owner_typeOrganization
is_verifiedyes
owner_loginmicrosoft
public_repos8,310
account_age_days4,672

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

63Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
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/igvm
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://docs.rs/igvm
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

69Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
6.8/7.5Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
0/5Packaging — no data
0.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
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 — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.9
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

66Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 96 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.99
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — igvm_c/Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
2/10Demonstrated agent practice — 1 of the last 98 commits agent-authored or agent-credited
8/8Automated maintenance — 1 of the last 98 commits are automated dependency updates
1/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_filesigvm_c/Makefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.01
toolchain_manifestsCargo.toml, igvm/Cargo.toml, igvm_c/test_data/Cargo.toml, igvm_defs/Cargo.toml
dependency_bot_commit_share0.01
How it's scored
45/45Type-checkable code — Rust (statically typed)
52.2/55Manageable file sizes — 1/20 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes215,501
source_files_sampled20
oversized_source_files1
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 — sample
Inputs used
example_dirssample
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

155GitHub stars
25contributors
26commits, last 12 months
1days since last push
3releases
3bus factor
18open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index crates:igvm@0.5.0; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 42 ⇿
0Stars
42Forks
3Releases

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.

010203040504232023-082025-032026-09
Major 0Minor 0Patch 0

Each point covers 3 days.

OpenSSF Scorecard 6.9 / 10
6.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-26 02:29 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-Tests30 out of 30 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
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
9Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
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 17
RegistryPackageVersion constraintManifest
crates.ioigvm_defs—igvm/Cargo.toml
crates.iobitfield-struct—igvm/Cargo.toml
crates.iocorim—igvm/Cargo.toml
crates.iorange_map_vec—igvm/Cargo.toml
crates.iocrc32fast—igvm/Cargo.toml
crates.iohex—igvm/Cargo.toml
crates.ioopen-enum—igvm/Cargo.toml
crates.iosha2—igvm/Cargo.toml
crates.iothiserror—igvm/Cargo.toml
crates.iotracing—igvm/Cargo.toml
crates.iouuid—igvm/Cargo.toml
crates.iozerocopy—igvm/Cargo.toml
crates.iostatic_assertions—igvm/Cargo.toml
crates.iobitfield-struct—igvm_defs/Cargo.toml
crates.ioopen-enum—igvm_defs/Cargo.toml
crates.iostatic_assertions—igvm_defs/Cargo.toml
crates.iozerocopy—igvm_defs/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.

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.