Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-06 02:40 UTC

xmlresolver / xmlresolvercs

A C# implementation of the XML Resolver

C#No license detected★ 4 stars⑂ 4 forkssince Jun 2021View on GitHub ↗

xmlresolver/xmlresolvercs holds a health index of 35 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (59/100) and lowest on Engineering Quality (27/100). It was last updated 124 days ago. A single contributor accounts for most of its recent work.

35
overall / 100
Weak

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.

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

Ownership

XML ResolverOrganization
3 followers10 public repossince May 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetXmlResolver6.1.1-430 days agoxmlxmlresolver

Metrics by category

Vitality

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

36Weak · 21% of overall
How it's scored
9.9/36Push recencylast push 124 days ago
2.8/36Commit cadence4/52 weeks with commits
14/18Commit volume35 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year35
human_commit_share1
days_since_last_push124
active_weeks_last_year4
How it's scored
16.2/27Ships releases33 version tags (no GitHub releases)
16.2/36Release recencylatest release 197 days ago
12.6/27Release cadencea release every ~142.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count33
latest_release_tag6.0.22
releases_from_tagsyes
days_since_latest_release197
mean_days_between_releases142.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?

33At Risk · 17% of overall
How it's scored
7.7/60Stars4 stars
4/25Forks4 forks
0/15Watchers1 watchers
Inputs used
forks4
stars4
watchers1
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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
62.4/80Total downloads1,021,078 downloads all-time across nuget
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesXmlResolver
dependents
ecosystemsnuget
total_downloads1,021,078
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.7/22.5Commit distributiontop contributor authored 97% of commits
2.7/13.5Contributor breadth2 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.968
How it's scored
38.4/42Issue resolution91% of issues closed
29/30PR acceptance61/63 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 3/14 approved changesets -- score normalized to 2
Inputs used
merged_prs61
open_issues3
closed_issues32
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.914
closed_unmerged_prs2
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
4.3/25Owner reach3 followers of xmlresolver
18.2/25Track record10 public repos, account ~5 yr old
Inputs used
followers3
owner_typeOrganization
is_verifiedno
owner_loginxmlresolver
public_repos10
account_age_days1,932

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

27At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests9 out of 13 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/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_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
6.8/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
1.5/2.5CI-Tests9 out of 13 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 3/14 approved changesets -- score normalized to 2
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate2.5
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages18
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 18 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
21.3/40Legible commit history40 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.4
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapMovedToCodeberg/DataTests/DataTests.csproj, MovedToCodeberg/SampleApp/SampleApp.csproj, MovedToCodeberg/UnitTests/UnitTests.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsMovedToCodeberg/DataTests/DataTests.csproj, MovedToCodeberg/SampleApp/SampleApp.csproj, MovedToCodeberg/UnitTests/UnitTests.csproj, MovedToCodeberg/XmlResolver/XmlResolver.csproj, MovedToCodeberg/build.gradle
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeC# (statically typed)
55/55Manageable file sizes0/90 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes34,771
source_files_sampled90
oversized_source_files0
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 examplessample
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

4GitHub stars
2contributors
35commits, last 12 months
124days since last push
33releases
1bus factor
3open issues
Mavenpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 4 ⇿
0Stars
4Forks
31Releases

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.

1223344412021-082023-102026-01
Major 3Minor 12Patch 16

Each point covers 4 days.

OpenSSF Scorecard 2.5 / 10
2.5aggregate

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-06 02:39 UTC

9Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
6CI-Tests9 out of 13 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 3/14 approved changesets -- score normalized to 2
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 23
RegistryPackageVersion constraintManifest
NuGetMicrosoft.NET.Test.Sdk17.11.1MovedToCodeberg/DataTests/DataTests.csproj
NuGetNUnit4.2.2MovedToCodeberg/DataTests/DataTests.csproj
NuGetNUnit3TestAdapter4.6.0MovedToCodeberg/DataTests/DataTests.csproj
NuGetNUnit.Analyzers4.4.0MovedToCodeberg/DataTests/DataTests.csproj
NuGetcoverlet.collector6.0.2MovedToCodeberg/DataTests/DataTests.csproj
NuGetNuGet.Frameworks7.0.1MovedToCodeberg/SampleApp/SampleApp.csproj
NuGetSystem.IO.Packaging10.0.1MovedToCodeberg/SampleApp/SampleApp.csproj
NuGetXmlResolverData6.0.3MovedToCodeberg/SampleApp/SampleApp.csproj
NuGetMicrosoft.NET.Test.Sdk16.9.4MovedToCodeberg/UnitTests/UnitTests.csproj
NuGetNuGet.Frameworks7.0.1MovedToCodeberg/UnitTests/UnitTests.csproj
NuGetNUnit3.13.1MovedToCodeberg/UnitTests/UnitTests.csproj
NuGetNUnit3TestAdapter3.17.0MovedToCodeberg/UnitTests/UnitTests.csproj
NuGetcoverlet.collector6.0.4MovedToCodeberg/UnitTests/UnitTests.csproj
NuGetSystem.IO.Packaging10.0.1MovedToCodeberg/UnitTests/UnitTests.csproj
NuGetXmlResolverData6.0.3MovedToCodeberg/UnitTests/UnitTests.csproj
NuGetMicrosoft.Extensions.Configuration10.0.1MovedToCodeberg/XmlResolver/XmlResolver.csproj
NuGetMicrosoft.Extensions.Configuration.Json10.0.1MovedToCodeberg/XmlResolver/XmlResolver.csproj
NuGetMicrosoft.Extensions.Configuration.Xml10.0.1MovedToCodeberg/XmlResolver/XmlResolver.csproj
NuGetNLog6.0.7MovedToCodeberg/XmlResolver/XmlResolver.csproj
NuGetSystem.IO.Packaging10.0.1MovedToCodeberg/XmlResolver/XmlResolver.csproj
NuGetSystem.Collections.Immutable10.0.1MovedToCodeberg/XmlResolver/XmlResolver.csproj
NuGetIndexRange1.1.0MovedToCodeberg/XmlResolver/XmlResolver.csproj
NuGetNuGet.Frameworks7.0.1MovedToCodeberg/XmlResolver/XmlResolver.csproj
All dependencies 18

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

RegistryPackageVersionRelation
NuGetcoverlet.collector6.0.2direct
NuGetcoverlet.collector6.0.4direct
NuGetIndexRange1.1.0direct
NuGetMicrosoft.Extensions.Configuration10.0.1direct
NuGetMicrosoft.Extensions.Configuration.Json10.0.1direct
NuGetMicrosoft.Extensions.Configuration.Xml10.0.1direct
NuGetMicrosoft.NET.Test.Sdk16.9.4direct
NuGetMicrosoft.NET.Test.Sdk17.11.1direct
NuGetNLog6.0.7direct
NuGetNuGet.Frameworks7.0.1direct
NuGetNUnit3.13.1direct
NuGetNUnit4.2.2direct
NuGetNUnit.Analyzers4.4.0direct
NuGetNUnit3TestAdapter3.17.0direct
NuGetNUnit3TestAdapter4.6.0direct
NuGetSystem.Collections.Immutable10.0.1direct
NuGetSystem.IO.Packaging10.0.1direct
NuGetXmlResolverData6.0.3direct
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 18 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct.

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