Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-18 13:55 UTC

oneblink / sdk-dotnet

OneBlink SDK to serve as an entry point for all OneBlink Services in .Net

C#MIT★ 0 stars⑂ 3 forkssince Jun 2019View on GitHub ↗

oneblink/sdk-dotnet holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (95/100) and lowest on AI Readiness (40/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

OneBlinkOrganization · verified domain
8 followers100 public repossince Sep 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetOneBlink.SDK13.1.4-1341 day agooneblinkforms

Metrics by category

Vitality

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

95Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
27/36Commit cadence — 39/52 weeks with commits
18/18Commit volume — 148 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year148
human_commit_share0.99
days_since_last_push0
active_weeks_last_year39

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~24.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv13.1.4
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases24.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?

45Weak · 17% of overall
How it's scored
0/60Stars — 0 stars
2.5/25Forks — 3 forks
0/15Watchers — 1 watchers
Inputs used
forks3
stars0
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, github.com
has_pull_request_templateyes
How it's scored
55.1/80Total downloads — 199,554 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesOneBlink.SDK
dependents—
ecosystemsnuget
total_downloads199,554
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?

68Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
14.6/22.5Commit distribution — top contributor authored 35% of commits
13.5/13.5Contributor breadth — 11 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor2
contributors_sampled11
top_contributor_share0.35
How it's scored
0/42Issue resolution — 0% of issues closed
29.6/30PR acceptance — 427/433 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 7/18 approved changesets -- score normalized to 3
Inputs used
merged_prs427
open_issues1
closed_issues0
prs_merged_7d1
prs_decided_7d1
prs_merged_30d4
prs_decided_30d4
issue_closed_ratio0
closed_unmerged_prs6
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
20/20Verified domain
6.9/25Owner reach — 8 followers of oneblink
25/25Track record — 100 public repos, account ~14 yr old
Inputs used
followers8
owner_typeOrganization
is_verifiedyes
owner_loginoneblink
public_repos100
account_age_days5,171

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

49Weak · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests — 1 out of 7 merged PRs checked by a CI test -- score normalized to 1
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/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_diryes
has_descriptionyes

Security

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

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0.2/2.5CI-Tests — 1 out of 7 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 7/18 approved changesets -- score normalized to 3
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflow — 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 — 30 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
1.5/5SAST — SAST tool is not run on all commits -- score normalized to 3
2/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages13
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 13 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.

40Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
15.6/40Legible commit history — 29 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.293
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — OneBlink.SDK.Tests/OneBlink.SDK.Tests.csproj, OneBlink.SDK/OneBlink.SDK.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — C# (statically typed)
0/10Reproducible environment
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 1 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.02
toolchain_manifestsOneBlink.SDK.Tests/OneBlink.SDK.Tests.csproj, OneBlink.SDK/OneBlink.SDK.csproj
dependency_bot_commit_share0.01
How it's scored
45/45Type-checkable code — C# (statically typed)
55/55Manageable file sizes — 0/207 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes39,093
source_files_sampled207
oversized_source_files0

Key facts

0GitHub stars
11contributors
148commits, last 12 months
0days since last push
100releases
2bus factor
1open issues
NuGetpackage ecosystems

More detail

Star and fork history 0 ★ / 3 ⇿
0Stars
3Forks
89Releases

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.

111222212021-042023-102026-03
Major 7Minor 12Patch 36

Each point covers 5 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-11-18 13:54 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
1CI-Tests1 out of 7 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 7/18 approved changesets -- score normalized to 3
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 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
3SASTSAST tool is not run on all commits -- score normalized to 3
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 13
RegistryPackageVersion constraintManifest
NuGetdotenv.net3.1.1OneBlink.SDK.Tests/OneBlink.SDK.Tests.csproj
NuGetGitHubActionsTestLogger1.4.1OneBlink.SDK.Tests/OneBlink.SDK.Tests.csproj
NuGetMicrosoft.NET.Test.Sdk17.1.0OneBlink.SDK.Tests/OneBlink.SDK.Tests.csproj
NuGetxunit2.4.1OneBlink.SDK.Tests/OneBlink.SDK.Tests.csproj
NuGetxunit.runner.visualstudio2.4.3OneBlink.SDK.Tests/OneBlink.SDK.Tests.csproj
NuGetAWSSDK.SimpleEmail3.7.0.150OneBlink.SDK/OneBlink.SDK.csproj
NuGetMailKit4.16.0OneBlink.SDK/OneBlink.SDK.csproj
NuGetMicrosoft.CSharp4.7.0OneBlink.SDK/OneBlink.SDK.csproj
NuGetSystem.IdentityModel.Tokens.Jwt6.34.0OneBlink.SDK/OneBlink.SDK.csproj
NuGetNewtonsoft.Json13.0.4OneBlink.SDK/OneBlink.SDK.csproj
NuGetAWSSDK.Core3.7.10.11OneBlink.SDK/OneBlink.SDK.csproj
NuGetAWSSDK.S33.7.8.23OneBlink.SDK/OneBlink.SDK.csproj
NuGetMicrosoft.SourceLink.GitHub1.1.1OneBlink.SDK/OneBlink.SDK.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
NuGetAWSSDK.Core3.7.10.11direct
NuGetAWSSDK.S33.7.8.23direct
NuGetAWSSDK.SimpleEmail3.7.0.150direct
NuGetdotenv.net3.1.1direct
NuGetGitHubActionsTestLogger1.4.1direct
NuGetMailKit4.16.0direct
NuGetMicrosoft.CSharp4.7.0direct
NuGetMicrosoft.NET.Test.Sdk17.1.0direct
NuGetMicrosoft.SourceLink.GitHub1.1.1direct
NuGetNewtonsoft.Json13.0.4direct
NuGetSystem.IdentityModel.Tokens.Jwt6.34.0direct
NuGetxunit2.4.1direct
NuGetxunit.runner.visualstudio2.4.3direct
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 13 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 statistics — NuGet.