Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-16 12:37 UTC

aaubry / YamlDotNet

YamlDotNet is a .NET library for YAML

C#MIT★ 2,843 stars⑂ 515 forkssince Oct 2012View on GitHub ↗

aaubry/YamlDotNet holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (87/100) and lowest on AI Readiness (42/100). It was last updated 19 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

Antoine AubryPersonal account
127 followers50 public repossince Feb 2011

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetYamlDotNet18.1.0-5919 days agoyamlparserdevelopmentlibraryserialization

Metrics by category

Vitality

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

76Good · 21% of overall
How it's scored
28.8/36Push recencylast push 19 days ago
9/36Commit cadence13/52 weeks with commits
18/18Commit volume103 commits in the last year
10/10OpenSSF Scorecard: Maintained28 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year103
human_commit_share
days_since_last_push19
active_weeks_last_year13
How it's scored
27/27Ships releases93 releases published
36/36Release recencylatest release 19 days ago
19.8/27Release cadencea release every ~72.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count93
latest_release_tagv18.1.0
releases_from_tagsno
days_since_latest_release19
mean_days_between_releases72.4
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?

87Excellent · 17% of overall
How it's scored
56/60Stars2,843 stars
22.6/25Forks515 forks
9.8/15Watchers59 watchers
Inputs used
forks515
stars2,843
watchers59
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
80/80Total downloads512,386,668 downloads all-time across nuget
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesYamlDotNet
dependents
ecosystemsnuget
total_downloads512,386,668
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?

71Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.4/22.5Commit distributiontop contributor authored 49% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 17 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled100
top_contributor_share0.494
How it's scored
34.8/42Issue resolution83% of issues closed
24.2/30PR acceptance312/387 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 1/8 approved changesets -- score normalized to 1
Inputs used
merged_prs312
open_issues111
closed_issues533
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.828
closed_unmerged_prs75
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
15.1/25Owner reach127 followers of aaubry
24.4/25Track record50 public repos, account ~15 yr old
Inputs used
followers127
owner_typeUser
is_verified
owner_loginaaubry
public_repos50
account_age_days5,623
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on nuget
35/35Publish recencylatest publish 19 days ago
20/20Version history59 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesYamlDotNet
ecosystemsnuget
any_deprecatedno
min_days_since_publish19

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests6 out of 6 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsyaml, serialization, dotnet, parser
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests6 out of 6 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
0.8/7.5Code-ReviewFound 1/8 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 17 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained28 commit(s) and 6 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
4.5/5SASTSAST tool detected but not run on all commits
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.4
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.

42Weak · 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
22/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
10/10Reproducible environmentDockerfile
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_testsyes
lockfiles
has_dockerfileyes
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. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeC# (statically typed)
54.5/55Manageable file sizes3/349 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes97,863
source_files_sampled349
oversized_source_files3

Key facts

2,843GitHub stars
100contributors
103commits, last 12 months
19days since last push
93releases
2bus factor
111open issues
NuGetpackage ecosystems

Data collection warnings

  • Could not fetch nuget package 'YamlDotNet.Analyzers.StaticGenerator' from its registry

More detail

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-16 12:37 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests6 out of 6 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 1/8 approved changesets -- score normalized to 1
10Contributorsproject has 17 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained28 commit(s) and 6 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
9SASTSAST tool detected but not run on all commits
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.CodeAnalysis.CSharpYamlDotNet.Analyzers.StaticGenerator/YamlDotNet.Analyzers.StaticGenerator.csproj
NuGetMicrosoft.CodeAnalysis.AnalyzersYamlDotNet.Analyzers.StaticGenerator/YamlDotNet.Analyzers.StaticGenerator.csproj
NuGetBenchmarkDotNetYamlDotNet.Benchmark/YamlDotNet.Benchmark.csproj
NuGetSystem.Collections.ImmutableYamlDotNet.Benchmark/YamlDotNet.Benchmark.csproj
NuGetSystem.Reflection.MetadataYamlDotNet.Benchmark/YamlDotNet.Benchmark.csproj
NuGetMicrosoft.NET.Test.SdkYamlDotNet.Samples/YamlDotNet.Samples.csproj
NuGetxunitYamlDotNet.Samples/YamlDotNet.Samples.csproj
NuGetxunit.runner.visualstudioYamlDotNet.Samples/YamlDotNet.Samples.csproj
NuGetFluentAssertionsYamlDotNet.Test/YamlDotNet.Test.csproj
NuGetMicrosoft.NET.Test.SdkYamlDotNet.Test/YamlDotNet.Test.csproj
NuGetxunitYamlDotNet.Test/YamlDotNet.Test.csproj
NuGetxunit.runner.visualstudioYamlDotNet.Test/YamlDotNet.Test.csproj
NuGetFakeItEasyYamlDotNet.Test/YamlDotNet.Test.csproj
NuGetNullableYamlDotNet/YamlDotNet.csproj
All dependencies 16

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

RegistryPackageVersionRelation
NuGetBenchmarkDotNetdirect
NuGetFakeItEasydirect
NuGetFluentAssertionsdirect
NuGetMicrosoft.CodeAnalysis.Analyzersdirect
NuGetMicrosoft.CodeAnalysis.CSharpdirect
NuGetMicrosoft.NET.Test.Sdkdirect
NuGetNullabledirect
NuGetSystem.Collections.Immutabledirect
NuGetSystem.Reflection.Metadatadirect
NuGetxunitdirect
NuGetxunit.runner.visualstudiodirect
NuGetBullseyeindirect
NuGetcoverlet.collectorindirect
NuGetFSharp.Coreindirect
NuGetMicrosoft.AspNet.WebApi.Clientindirect
NuGetSimpleExecindirect
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 statisticsNuGet.