Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 14:25 UTC

finbourne / scheduler-sdk-csharp

Automated job scheduler service OpenAPI generated C# client SDK

C#MIT★ 0 stars⑂ 0 forkssince Nov 2023View on GitHub ↗

finbourne/scheduler-sdk-csharp holds a health index of 47 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (64/100) and lowest on AI Readiness (29/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

FINBOURNEOrganization · verified domain
42 followers147 public repossince Sep 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetFinbourne.Scheduler.Sdk2.4.6-1711 day agofinbournelusidsdk

Metrics by category

Vitality

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

32At Risk · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
6.2/36Commit cadence — 9/52 weeks with commits
9/18Commit volume — 9 commits in the last year
2/10OpenSSF Scorecard: Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year9
human_commit_share1
days_since_last_push1
active_weeks_last_year9
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

50Moderate · 17% of overall
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
3.3/15Watchers — 5 watchers
Inputs used
forks0
stars0
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateyes
How it's scored
54.4/80Total downloads — 170,592 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesFinbourne.Scheduler.Sdk
dependents—
ecosystemsnuget
total_downloads170,592
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.4/22.5Commit distribution — top contributor authored 71% of commits
2.7/13.5Contributor breadth — 2 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.714
How it's scored
0/42Issue resolution — no issues or no data
30/30PR acceptance — 1/1 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs1
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
11.7/25Owner reach — 42 followers of finbourne
25/25Track record — 147 public repos, account ~10 yr old
Inputs used
followers42
owner_typeOrganization
is_verifiedyes
owner_loginfinbourne
public_repos147
account_age_days3,650

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 — 171 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesFinbourne.Scheduler.Sdk
ecosystemsnuget
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
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?

46Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 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
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
1.5/7.5Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not 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_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.2
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, 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_packages11
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 11 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.

29At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — 0 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — sdk/Finbourne.Scheduler.Sdk/Finbourne.Scheduler.Sdk.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
0/8Automated maintenance — no automated dependency updates observed
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_manifestssdk/Finbourne.Scheduler.Sdk/Finbourne.Scheduler.Sdk.csproj
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — C# (statically typed)
53.1/55Manageable file sizes — 3/87 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes152,985
source_files_sampled87
oversized_source_files3

Key facts

0GitHub stars
2contributors
9commits, last 12 months
1days since last push
0releases
1bus factor
0open issues
—package ecosystems

More detail

OpenSSF Scorecard 3.2 / 10
3.2aggregate

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-18 14:25 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
2Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
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 11
RegistryPackageVersion constraintManifest
NuGetJsonSubTypes2.0.1sdk/Finbourne.Scheduler.Sdk/Finbourne.Scheduler.Sdk.csproj
NuGetNewtonsoft.Json13.0.3sdk/Finbourne.Scheduler.Sdk/Finbourne.Scheduler.Sdk.csproj
NuGetFinbourne.Sdk.Core0.0.6sdk/Finbourne.Scheduler.Sdk/Finbourne.Scheduler.Sdk.csproj
NuGetPolly7.2.3sdk/Finbourne.Scheduler.Sdk/Finbourne.Scheduler.Sdk.csproj
NuGetSystem.ComponentModel.Annotations5.0.0sdk/Finbourne.Scheduler.Sdk/Finbourne.Scheduler.Sdk.csproj
NuGetMicrosoft.Extensions.Configuration.Binder6.0.0sdk/Finbourne.Scheduler.Sdk/Finbourne.Scheduler.Sdk.csproj
NuGetMicrosoft.Extensions.Configuration.Json6.0.0sdk/Finbourne.Scheduler.Sdk/Finbourne.Scheduler.Sdk.csproj
NuGetMicrosoft.Extensions.Configuration.Abstractions6.0.0sdk/Finbourne.Scheduler.Sdk/Finbourne.Scheduler.Sdk.csproj
NuGetSystem.Text.Json6.0.10sdk/Finbourne.Scheduler.Sdk/Finbourne.Scheduler.Sdk.csproj
NuGetSystem.Text.RegularExpressions4.3.1sdk/Finbourne.Scheduler.Sdk/Finbourne.Scheduler.Sdk.csproj
NuGetSystem.Net.Http4.3.4sdk/Finbourne.Scheduler.Sdk/Finbourne.Scheduler.Sdk.csproj
All dependencies 11

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

RegistryPackageVersionRelation
NuGetFinbourne.Sdk.Core0.0.6direct
NuGetJsonSubTypes2.0.1direct
NuGetMicrosoft.Extensions.Configuration.Abstractions6.0.0direct
NuGetMicrosoft.Extensions.Configuration.Binder6.0.0direct
NuGetMicrosoft.Extensions.Configuration.Json6.0.0direct
NuGetNewtonsoft.Json13.0.3direct
NuGetPolly7.2.3direct
NuGetSystem.ComponentModel.Annotations5.0.0direct
NuGetSystem.Net.Http4.3.4direct
NuGetSystem.Text.Json6.0.10direct
NuGetSystem.Text.RegularExpressions4.3.1direct
Dependency advisories 0

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