Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-18 22:19 UTC

Open-NET-Libraries / Open.Serialization

DI/IoC agnostic interfaces for injecting any serialization library.

C#MIT★ 15 stars⑂ 2 forkssince Oct 2019View on GitHub ↗

Open-NET-Libraries/Open.Serialization holds a health index of 27 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (50/100) and lowest on Vitality (18/100). It was last updated 642 days ago. A single contributor accounts for most of its recent work.

27
overall / 100
At Risk

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.

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

Ownership

Open-NET-LibrariesOrganization
57 followers42 public repossince Jul 2020

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?

18Critical · 21% of overall
How it's scored
0/36Push recencylast push 642 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 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_year0
human_commit_share
days_since_last_push642
active_weeks_last_year0
How it's scored
27/27Ships releases1 releases published
0/36Release recencylatest release 2,378 days ago
12.6/27Release cadencecadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count1
latest_release_tagv2.2.4
releases_from_tagsno
days_since_latest_release2,378
mean_days_between_releases
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
18.6/60Stars15 stars
0/25Forks2 forks
0/15Watchers1 watchers
Inputs used
forks2
stars15
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
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?

50Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.4/22.5Commit distributiontop contributor authored 94% of commits
5.4/13.5Contributor breadth4 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.94
How it's scored
28/42Issue resolution67% of issues closed
22.5/30PR acceptance3/4 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 2/26 approved changesets -- score normalized to 0
Inputs used
merged_prs3
open_issues1
closed_issues2
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.667
closed_unmerged_prs1
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
12.7/25Owner reach57 followers of Open-NET-Libraries
23.9/25Track record42 public repos, account ~6 yr old
Inputs used
followers57
owner_typeOrganization
is_verified
owner_loginOpen-NET-Libraries
public_repos42
account_age_days2,198
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

28At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
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/10Topics13 topics
10/10Wiki
Inputs used
topicsdotnet, dotnet-core, dotnetcore, dotnet-standard, dotnetstandard, serialization, json, newtonsoft, utf8json, system-text-json, di, ioc, dependency-injection
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?

36Weak · 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
0/2.5CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 2/26 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file 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-Dependenciesno data
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_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

25At Risk · 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
11/11Static type checkingC# (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
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, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeC# (statically typed)
55/55Manageable file sizes0/74 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes13,416
source_files_sampled74
oversized_source_files0

Key facts

15GitHub stars
4contributors
0commits, last 12 months
642days since last push
1releases
1bus factor
1open issues
NuGetpackage ecosystems

More detail

OpenSSF Scorecard 3.6 / 10
3.6aggregate

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-18 22:19 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/26 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
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 19
RegistryPackageVersion constraintManifest
NuGetMicrosoft.SourceLink.GitHub1.1.1Open.Serialization.Json.Newtonsoft/Open.Serialization.Json.Newtonsoft.csproj
NuGetMicrosoft.Extensions.DependencyInjection6.0.0Open.Serialization.Json.Newtonsoft/Open.Serialization.Json.Newtonsoft.csproj
NuGetNewtonsoft.Json11.0.1Open.Serialization.Json.Newtonsoft/Open.Serialization.Json.Newtonsoft.csproj
NuGetMicrosoft.SourceLink.GitHub1.1.1Open.Serialization.Json.System/Open.Serialization.Json.System.csproj
NuGetMicrosoft.Extensions.DependencyInjection6.0.0Open.Serialization.Json.System/Open.Serialization.Json.System.csproj
NuGetSystem.Text.Json6.0.10Open.Serialization.Json.System/Open.Serialization.Json.System.csproj
NuGetMicrosoft.SourceLink.GitHub1.1.1Open.Serialization.Json.Utf8Json/Open.Serialization.Json.Utf8Json.csproj
NuGetMicrosoft.Extensions.DependencyInjection6.0.0Open.Serialization.Json.Utf8Json/Open.Serialization.Json.Utf8Json.csproj
NuGetUtf8Json1.3.7Open.Serialization.Json.Utf8Json/Open.Serialization.Json.Utf8Json.csproj
NuGetMicrosoft.SourceLink.GitHub1.1.1Open.Serialization.Json/Open.Serialization.Json.csproj
NuGetFluentAssertions6.7.0Open.Serialization.Tests/Open.Serialization.Tests.csproj
NuGetMicrosoft.NET.Test.Sdk17.2.0Open.Serialization.Tests/Open.Serialization.Tests.csproj
NuGetNewtonsoft.Json13.0.1Open.Serialization.Tests/Open.Serialization.Tests.csproj
NuGetxunit2.4.1Open.Serialization.Tests/Open.Serialization.Tests.csproj
NuGetxunit.runner.visualstudio2.4.5Open.Serialization.Tests/Open.Serialization.Tests.csproj
NuGetcoverlet.collector3.1.2Open.Serialization.Tests/Open.Serialization.Tests.csproj
NuGetMicrosoft.SourceLink.GitHub1.1.1Open.Serialization/Open.Serialization.csproj
NuGetSystem.Memory4.5.4Open.Serialization/Open.Serialization.csproj
NuGetSystem.Threading.Tasks.Extensions4.5.4Open.Serialization/Open.Serialization.csproj
All dependencies 13

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

RegistryPackageVersionRelation
NuGetcoverlet.collector3.1.2direct
NuGetFluentAssertions6.7.0direct
NuGetMicrosoft.Extensions.DependencyInjection6.0.0direct
NuGetMicrosoft.NET.Test.Sdk17.2.0direct
NuGetMicrosoft.SourceLink.GitHub1.1.1direct
NuGetNewtonsoft.Json11.0.1direct
NuGetNewtonsoft.Json13.0.1direct
NuGetSystem.Memory4.5.4direct
NuGetSystem.Text.Json6.0.10direct
NuGetSystem.Threading.Tasks.Extensions4.5.4direct
NuGetUtf8Json1.3.7direct
NuGetxunit2.4.1direct
NuGetxunit.runner.visualstudio2.4.5direct
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.14.0 — full methodology · metrics wiki.

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