Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-24 05:39 UTC

ARKlab / MessagePack

Support for NodaTime types to MessagePack C#.

C#MIT★ 12 stars⑂ 4 forkssince Apr 2018View on GitHub ↗

ARKlab/MessagePack holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (90/100) and lowest on AI Readiness (47/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

ARK EnergyOrganization
3 followers25 public repossince Jun 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetMessagePack.NodaTime3.5.9-300 days agomessagepackmsgpacknodatimeserializeserializationarkc#formatterresolverdatetimevisualstudioframework

Metrics by category

Vitality

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

90Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
19.4/36Commit cadence — 28/52 weeks with commits
17.8/18Commit volume — 95 commits in the last year
10/10OpenSSF Scorecard: Maintained — 26 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year95
human_commit_share0.21
days_since_last_push0
active_weeks_last_year28

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 23 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~34.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count23
latest_release_tagv3.5.9
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases34.6
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?

49Weak · 17% of overall
How it's scored
16.9/60Stars — 12 stars
4/25Forks — 4 forks
6/15Watchers — 13 watchers
Inputs used
forks4
stars12
watchers13
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
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
65.5/80Total downloads — 2,006,024 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesMessagePack.NodaTime
dependents—
ecosystemsnuget
total_downloads2,006,024
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.6/22.5Commit distribution — top contributor authored 62% of commits
5.4/13.5Contributor breadth — 4 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.617
How it's scored
31.5/42Issue resolution — 75% of issues closed
24.8/30PR acceptance — 137/166 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/1 approved changesets -- score normalized to 0
Inputs used
merged_prs137
open_issues1
closed_issues3
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.75
closed_unmerged_prs29
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 backing — organization-owned
0/20Verified domain
4.3/25Owner reach — 3 followers of ARKlab
22.3/25Track record — 25 public repos, account ~14 yr old
Inputs used
followers3
owner_typeOrganization
is_verifiedno
owner_loginARKlab
public_repos25
account_age_days5,224

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on nuget
35/35Publish recency — latest publish 0 days ago
20/20Version history — 30 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesMessagePack.NodaTime
ecosystemsnuget
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

54Moderate · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 12 out of 12 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
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/10Topics — 5 topics
10/10Wiki
Inputs used
topicsmessagepack, nodatime, msgpack, c-sharp, serialization
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?

67Good · 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
2.5/2.5CI-Tests — 12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/1 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
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
7.5/7.5Maintained — 26 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
5/5SAST — SAST tool is run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
6/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.9
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
How it's scored
12/35Direct dependencies free of known advisories — 1 affected: MessagePack 2.1.80 (high 8.2)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
33.2/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,427 days ago
Inputs used
sourceosv
advisories13
affected_packages1
assessed_packages30
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 30 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.

47Weak · 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 — 18 of 21 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.857
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — MessagePack.NodaTime.Tests/MessagePack.NodaTime.Tests.csproj, MessagePack.NodaTime/MessagePack.NodaTime.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — C# (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 74 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsMessagePack.NodaTime.Tests/MessagePack.NodaTime.Tests.csproj, MessagePack.NodaTime/MessagePack.NodaTime.csproj
dependency_bot_commit_share0.74
How it's scored
45/45Type-checkable code — C# (statically typed)
55/55Manageable file sizes — 0/26 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes5,094
source_files_sampled26
oversized_source_files0

Key facts

12GitHub stars
4contributors
95commits, last 12 months
0days since last push
23releases
1bus factor
1open issues
NuGetpackage 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
6Releases

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.

1223344412018-052021-072024-10
Major 0Minor 2Patch 4

Each point covers 6 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-09-24 05:38 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/1 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained26 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
8Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
NuGetMicrosoft.NET.Test.Sdk18.10.1MessagePack.NodaTime.Tests/MessagePack.NodaTime.Tests.csproj
NuGetMicrosoft.Testing.Extensions.TrxReport2.4.1MessagePack.NodaTime.Tests/MessagePack.NodaTime.Tests.csproj
NuGetxunit.v34.0.1MessagePack.NodaTime.Tests/MessagePack.NodaTime.Tests.csproj
NuGetxunit.runner.visualstudio4.0.0MessagePack.NodaTime.Tests/MessagePack.NodaTime.Tests.csproj
NuGetMessagePack3.1.10MessagePack.NodaTime/MessagePack.NodaTime.csproj
NuGetNodaTime3.3.4MessagePack.NodaTime/MessagePack.NodaTime.csproj
All dependencies 30

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

RegistryPackageVersionRelation
NuGetMessagePack2.1.80direct
NuGetMessagePack3.1.10direct
NuGetMicrosoft.NET.Test.Sdk18.10.1direct
NuGetMicrosoft.Testing.Extensions.TrxReport2.4.1direct
NuGetNodaTime2.4.7direct
NuGetNodaTime3.3.4direct
NuGetxunit.runner.visualstudio2.4.1direct
NuGetxunit.runner.visualstudio4.0.0direct
NuGetxunit.v34.0.1direct
NuGetMessagePack.Annotations2.1.80indirect
NuGetMessagePackAnalyzer2.1.80indirect
NuGetMicrosoft.Bcl.AsyncInterfaces1.1.0indirect
NuGetMSTest.TestAdapter2.1.0indirect
NuGetMSTest.TestFramework2.1.0indirect
NuGetSystem.Buffers4.5.0indirect
NuGetSystem.Memory4.5.3indirect
NuGetSystem.Numerics.Vectors4.5.0indirect
NuGetSystem.Reflection.Emit4.7.0indirect
NuGetSystem.Reflection.Emit.Lightweight4.7.0indirect
NuGetSystem.Runtime.CompilerServices.Unsafe4.7.0indirect
NuGetSystem.Threading.Tasks.Extensions4.5.3indirect
NuGetSystem.ValueTuple4.5.0indirect
NuGetxunit2.4.1indirect
NuGetxunit.abstractions2.0.3indirect
NuGetxunit.analyzers0.10.0indirect
NuGetxunit.assert2.4.1indirect
NuGetxunit.core2.4.1indirect
NuGetxunit.extensibility.core2.4.1indirect
NuGetxunit.extensibility.execution2.4.1indirect
NuGetxunit.runner.console2.4.1indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
MessagePack2.1.80directhigh133.1.7

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