Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 22:47 UTC

microsoft / MSBuildPrediction

A library to predict inputs and outputs of MSBuild projects

C#MIT★ 43 stars⑂ 19 forkssince Jun 2019View on GitHub ↗

microsoft/MSBuildPrediction holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (72/100) and lowest on Engineering Quality (53/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

73
overall / 100
Good

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.

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

Ownership

MicrosoftOrganization · verified domain
132,146 followers8,381 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
NuGetMicrosoft.Build.Prediction1.2.44-2354 days agomsbuild

Metrics by category

Vitality

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

70Good · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
4.2/36Commit cadence — 6/52 weeks with commits
9.7/18Commit volume — 11 commits in the last year
6/10OpenSSF Scorecard: Maintained — 7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year11
human_commit_share0.97
days_since_last_push4
active_weeks_last_year6
How it's scored
27/27Ships releases — 36 releases published
36/36Release recency — latest release 54 days ago
19.8/27Release cadence — a release every ~74.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count36
latest_release_tagv1.2.44
releases_from_tagsno
days_since_latest_release54
mean_days_between_releases74.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?

54Moderate · 17% of overall
How it's scored
26.3/60Stars — 43 stars
10.5/25Forks — 19 forks
2.7/15Watchers — 4 watchers
Inputs used
forks19
stars43
watchers4
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_badges3
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesdev.azure.com, shields.io
has_pull_request_templateno
How it's scored
47.7/80Total downloads — 38,664 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesMicrosoft.Build.Prediction
dependents—
ecosystemsnuget
total_downloads38,664
monthly_downloads—
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?

72Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.1/22.5Commit distribution — top contributor authored 82% of commits
13.5/13.5Contributor breadth — 12 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled12
top_contributor_share0.816
How it's scored
29.4/42Issue resolution — 70% of issues closed
29.3/30PR acceptance — 135/138 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 20/28 approved changesets -- score normalized to 7
Inputs used
merged_prs135
open_issues3
closed_issues7
prs_merged_7d0
prs_decided_7d1
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0.7
closed_unmerged_prs3
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 132,146 followers of microsoft
25/25Track record — 8,381 public repos, account ~12 yr old
Inputs used
followers132,146
owner_typeOrganization
is_verifiedyes
owner_loginmicrosoft
public_repos8,381
account_age_days4,696

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on nuget
35/35Publish recency — latest publish 54 days ago
20/20Version history — 23 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesMicrosoft.Build.Prediction
ecosystemsnuget
any_deprecatedno
min_days_since_publish54

Engineering Quality

Are baseline engineering and documentation practices in place?

53Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests — 14 out of 30 merged PRs checked by a CI test -- score normalized to 4
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

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
6/7.5Branch-Protection — branch protection is not maximal on development and all release branches
1/2.5CI-Tests — 14 out of 30 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-Review — Found 20/28 approved changesets -- score normalized to 7
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
4.5/7.5Maintained — 7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
1/5SAST — SAST tool is not run on all commits -- score normalized to 2
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.9
Excluded from scoring (no data or not applicable): 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.

55Moderate · 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 — 84 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.866
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — src/BuildPrediction/Microsoft.Build.Prediction.csproj, src/BuildPredictionTests/Microsoft.Build.Prediction.Tests.csproj, src/BuildPredictionTests/TestsData/Copy/CopyCustomImportedTargets.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — C# (statically typed)
0/10Reproducible environment
8/10Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 2 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.04
toolchain_manifestssrc/BuildPrediction/Microsoft.Build.Prediction.csproj, src/BuildPredictionTests/Microsoft.Build.Prediction.Tests.csproj, src/BuildPredictionTests/TestsData/Copy/CopyCustomImportedTargets.csproj, src/BuildPredictionTests/TestsData/Copy/CopyDefaultCustomTargets.csproj, src/BuildPredictionTests/TestsData/Copy/CopyTestBatchingDestinationFolder.csproj, src/BuildPredictionTests/TestsData/Copy/CopyTestBatchingInputs.csproj, src/BuildPredictionTests/TestsData/Copy/DestinationFilesItemTransformation.csproj, src/BuildPredictionTests/TestsData/Copy/IncludeViaItemGroupCopy.csproj, src/BuildPredictionTests/TestsData/Copy/SourceFolders.csproj, src/BuildPredictionTests/TestsData/Copy/TargetConditionInCopy.csproj, src/BuildPredictionTests/TestsData/Copy/TargetDependsOnCopy.csproj, src/BuildPredictionTests/TestsData/Copy/TargetUnevaluatableConditionInCopy.csproj, src/BuildPredictionTests/TestsData/Copy/TaskConditionInCopy.csproj, src/BuildPredictionTests/TestsData/Copy/copyparsetimenotexistfile.csproj, src/BuildPredictionTests/TestsData/Copy/customTargetWithCopy.csproj, src/BuildPredictionTests/TestsData/Copy/destinationFilesCopy.csproj, src/BuildPredictionTests/TestsData/Copy/destinationFolderMultipleTargetsCopy.csproj, src/BuildPredictionTests/TestsData/Copy/wildcardsInIncludeCopy.csproj, src/BuildPredictionTests/TestsData/Import/NestedImports.csproj
dependency_bot_commit_share0.02
How it's scored
45/45Type-checkable code — C# (statically typed)
55/55Manageable file sizes — 0/132 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes36,112
source_files_sampled132
oversized_source_files0

Key facts

43GitHub stars
12contributors
11commits, last 12 months
4days since last push
36releases
1bus factor
3open issues
—package ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 19 ⇿
0Stars
19Forks
36Releases

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.

0481216201822019-062023-012026-09
Major 1Minor 12Patch 23

Each point covers 7 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-10-19 22:46 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
4CI-Tests14 out of 30 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 20/28 approved changesets -- score normalized to 7
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
6Maintained7 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 6
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
2SASTSAST tool is not run on all commits -- score normalized to 2
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 14
RegistryPackageVersion constraintManifest
NuGetMicrosoft.Bcl.HashCode—src/BuildPrediction/Microsoft.Build.Prediction.csproj
NuGetMicrosoft.Build—src/BuildPrediction/Microsoft.Build.Prediction.csproj
NuGetMicrosoft.Build.Framework—src/BuildPrediction/Microsoft.Build.Prediction.csproj
NuGetMicrosoft.Build.Utilities.Core—src/BuildPrediction/Microsoft.Build.Prediction.csproj
NuGetMicrosoft.Build—src/BuildPredictionTests/Microsoft.Build.Prediction.Tests.csproj
NuGetMicrosoft.Build.Framework—src/BuildPredictionTests/Microsoft.Build.Prediction.Tests.csproj
NuGetMicrosoft.Build.Locator—src/BuildPredictionTests/Microsoft.Build.Prediction.Tests.csproj
NuGetMicrosoft.Build.Utilities.Core—src/BuildPredictionTests/Microsoft.Build.Prediction.Tests.csproj
NuGetMicrosoft.NET.StringTools—src/BuildPredictionTests/Microsoft.Build.Prediction.Tests.csproj
NuGetMicrosoft.NET.Test.Sdk—src/BuildPredictionTests/Microsoft.Build.Prediction.Tests.csproj
NuGetSystem.Collections.Immutable—src/BuildPredictionTests/Microsoft.Build.Prediction.Tests.csproj
NuGetxunit.v3—src/BuildPredictionTests/Microsoft.Build.Prediction.Tests.csproj
NuGetxunit.analyzers—src/BuildPredictionTests/Microsoft.Build.Prediction.Tests.csproj
NuGetxunit.runner.visualstudio—src/BuildPredictionTests/Microsoft.Build.Prediction.Tests.csproj
All dependencies 11

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

RegistryPackageVersionRelation
NuGetMicrosoft.Bcl.HashCode—direct
NuGetMicrosoft.Build—direct
NuGetMicrosoft.Build.Framework—direct
NuGetMicrosoft.Build.Locator—direct
NuGetMicrosoft.Build.Utilities.Core—direct
NuGetMicrosoft.NET.StringTools—direct
NuGetMicrosoft.NET.Test.Sdk—direct
NuGetSystem.Collections.Immutable—direct
NuGetxunit.analyzers—direct
NuGetxunit.runner.visualstudio—direct
NuGetxunit.v3—direct
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 — NuGet.