Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-24 20:00 UTC

shinji-san / SecretSharingDotNet

An C# implementation of Shamir's Secret Sharing

C#MIT★ 50 stars⑂ 13 forkssince Jul 2019View on GitHub ↗

shinji-san/SecretSharingDotNet holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (86/100) and lowest on Sustainability & Governance (52/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

Sebastian WaltherPersonal account
9 followers6 public repossince Jul 2019

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
NuGetSecretSharingDotNet1.0.1-170 days agosecretsharingshamircryptography

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
23.5/36Commit cadence34/52 weeks with commits
18/18Commit volume517 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year517
human_commit_share0.96
days_since_last_push0
active_weeks_last_year34
How it's scored
27/27Ships releases18 releases published
36/36Release recencylatest release 0 days ago
12.6/27Release cadencea release every ~148.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count18
latest_release_tagv1.0.1
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases148.9
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?

54Moderate · 17% of overall
How it's scored
27.4/60Stars50 stars
9/25Forks13 forks
2.7/15Watchers4 watchers
Inputs used
forks13
stars50
watchers4
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
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, github.com, shields.io
has_pull_request_templateno
How it's scored
50.9/80Total downloads78,405 downloads all-time across nuget
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesSecretSharingDotNet
dependents
ecosystemsnuget
total_downloads78,405
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?

52Moderate · 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
4.1/13.5Contributor breadth3 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.998
How it's scored
36.8/42Issue resolution88% of issues closed
24.4/30PR acceptance304/374 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/13 approved changesets -- score normalized to 0
Inputs used
merged_prs304
open_issues2
closed_issues14
prs_merged_7d2
prs_decided_7d2
prs_merged_30d25
prs_decided_30d25
issue_closed_ratio0.875
closed_unmerged_prs70
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
7.2/25Owner reach9 followers of shinji-san
18.2/25Track record6 public repos, account ~7 yr old
Inputs used
followers9
owner_typeUser
is_verified
owner_loginshinji-san
public_repos6
account_age_days2,596
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 0 days ago
20/20Version history17 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesSecretSharingDotNet
ecosystemsnuget
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
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/10Topics9 topics
10/10Wiki
Inputs used
topicsdotnet-core, dotnet, csharp, csharp-library, secret-sharing, cryptography, shamir-secret-sharing, mit-license, dotnet-framework
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?

53Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests13 out of 13 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/7.5Code-ReviewFound 0/13 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflowdangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
4/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
5/5SASTSAST tool is run on all commits
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_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): 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.

70Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history96 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapsamples/SecretSharingDotNet.Demo.Console/SecretSharingDotNet.Demo.Console.csproj, src/SecretSharingDotNet.csproj, tests/SecretSharingDotNetTest.csproj (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance4 of the last 100 commits are automated dependency updates
8/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfilespackages.lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestssamples/SecretSharingDotNet.Demo.Console/SecretSharingDotNet.Demo.Console.csproj, src/SecretSharingDotNet.csproj, tests/SecretSharingDotNetTest.csproj
dependency_bot_commit_share0.04
How it's scored
45/45Type-checkable codeC# (statically typed)
53.4/55Manageable file sizes3/105 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes117,775
source_files_sampled105
oversized_source_files3
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 examplessamples
Inputs used
example_dirssamples
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

50GitHub stars
3contributors
517commits, last 12 months
0days since last push
18releases
1bus factor
2open issues
NuGetpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 13 ⇿
0Stars
13Forks
15Releases

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.

03581013151322020-012023-012026-01
Major 0Minor 11Patch 4

Each point covers 6 days.

OpenSSF Scorecard 5.3 / 10
5.3aggregate

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-08-24 19:59 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests13 out of 13 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/13 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
NuGetMicrosoft.NETFramework.ReferenceAssembliessrc/SecretSharingDotNet.csproj
NuGetMicrosoft.SourceLink.GitHubsrc/SecretSharingDotNet.csproj
NuGetSystem.Bufferssrc/SecretSharingDotNet.csproj
NuGetSystem.Bufferssrc/SecretSharingDotNet.csproj
NuGetSystem.Bufferssrc/SecretSharingDotNet.csproj
NuGetSystem.Bufferssrc/SecretSharingDotNet.csproj
All dependencies 12

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

RegistryPackageVersionRelation
NuGetMicrosoft.NETFramework.ReferenceAssembliesdirect
NuGetMicrosoft.SourceLink.GitHubdirect
NuGetSystem.Buffersdirect
NuGetCsCheckindirect
NuGetMicrosoft.Extensions.DependencyInjectionindirect
NuGetMicrosoft.NET.Test.Sdkindirect
NuGetMicrosoft.TestPlatform.ObjectModelindirect
NuGetMoqindirect
NuGetSystem.Memoryindirect
NuGetxunit.analyzersindirect
NuGetxunit.runner.visualstudioindirect
NuGetxunit.v3indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.