Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 01:35 UTC

dotnet / templating

This repo contains the Template Engine which is used by dotnet new

No license detected★ 1,742 stars⑂ 398 forkssince Jun 2016View on GitHub ↗

dotnet/templating holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Vitality (72/100) and lowest on AI Readiness (1/100). It was last updated today. A single contributor accounts for most of its recent work.

56
overall / 100
Moderate

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.

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

Ownership

.NET PlatformOrganization
22,978 followers278 public repossince Oct 2014

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

Metrics by category

Vitality

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

72Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
0.7/36Commit cadence1/52 weeks with commits
6.3/18Commit volume4 commits in the last year
10/10OpenSSF Scorecard: Maintained4 commit(s) and 26 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year4
human_commit_share
days_since_last_push0
active_weeks_last_year1

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 2 days ago
27/27Release cadencea release every ~14 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv10.0.302
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases14
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?

58Moderate · 17% of overall
How it's scored
52.6/60Stars1,742 stars
21.7/25Forks398 forks
11.3/15Watchers107 watchers
Inputs used
forks398
stars1,742
watchers107
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
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
0/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_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

59Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
40/42Issue resolution95% of issues closed
26.2/30PR acceptance7,465/8,550 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/4 approved changesets -- score normalized to 0
Inputs used
merged_prs7,465
open_issues83
closed_issues1,640
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.952
closed_unmerged_prs1,085
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.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach22,978 followers of dotnet
25/25Track record278 public repos, account ~11 yr old
Inputs used
followers22,978
owner_typeOrganization
is_verified
owner_logindotnet
public_repos278
account_age_days4,297
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.microsoft.com/dotnet/
10/10Repository description
10/10Topics2 topics
10/10Wiki
Inputs used
topicsdotnet, dotnet-template
has_wikiyes
homepagehttps://docs.microsoft.com/dotnet/
docs_sitehttps://docs.microsoft.com/dotnet/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/4 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
7.5/7.5Maintained4 commit(s) and 26 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/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not 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_aggregate4
Excluded from scoring (no data or not applicable): CI-Tests, 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.

1Critical · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno 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.
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageno
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. Remaining weights renormalized.

Key facts

1,742GitHub stars
1contributors
4commits, last 12 months
0days since last push
100releases
1bus factor
83open issues
package ecosystems

Data collection warnings

  • Language breakdown unavailable

More detail

OpenSSF Scorecard 4.0 / 10
4.0aggregate

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-17 01:35 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/4 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained4 commit(s) and 26 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
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 39

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

RegistryPackageVersionRelation
NuGetAwesomeAssertionsindirect
NuGetDrop.Appindirect
NuGetFakeItEasyindirect
NuGetJsonSchema.Netindirect
NuGetMicrosoft.AspNetCore1.0.3indirect
NuGetMicrosoft.AspNetCore.Mvc1.0.4indirect
NuGetMicrosoft.AspNetCore.StaticFiles1.0.1indirect
NuGetMicrosoft.Build.Frameworkindirect
NuGetMicrosoft.Build.Utilities.Coreindirect
NuGetMicrosoft.DotNet.IBCMergeindirect
NuGetMicrosoft.Extensions.Loggingindirect
NuGetMicrosoft.Extensions.Logging.Abstractionsindirect
NuGetMicrosoft.Extensions.Logging.Consoleindirect
NuGetMicrosoft.Extensions.Logging.Debug1.0.1indirect
NuGetMicrosoft.ManifestTool.CrossPlatformindirect
NuGetMicrosoft.NET.Test.Sdk15.0.0indirect
NuGetMicrosoft.TemplateEngine.Tasksindirect
NuGetMicrosoft.VisualStudio.Web.BrowserLink1.0.1indirect
NuGetMicrosoft.VisualStudioEng.MicroBuild.Coreindirect
NuGetMicrosoft.VisualStudioEng.MicroBuild.Plugins.SwixBuildindirect
NuGetNewtonsoft.Bla.Json13.0.3indirect
NuGetNewtonsoft.Json13.0.3indirect
NuGetNuGet.Configurationindirect
NuGetNuGet.Credentialsindirect
NuGetNuGet.Frameworksindirect
NuGetNuGet.Protocolindirect
NuGetPackageName_SpaceHolderindirect
NuGetSystem.CommandLineindirect
NuGetSystem.Text.Jsonindirect
NuGetVerify.DiffPlexindirect
NuGetVerify.Xunitindirect
NuGetVerify.XunitV3indirect
NuGetxunitindirect
NuGetxunit2.2.0indirect
NuGetxunit.abstractionsindirect
NuGetxunit.extensibility.executionindirect
NuGetxunit.runner.visualstudio2.2.0indirect
NuGetxunit.v3.assertindirect
NuGetxunit.v3.extensibility.coreindirect
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.11.0 — full methodology · metrics wiki.

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