Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-21 12:50 UTC

WildGums / Orc.DataAccess

C#Custom license★ 0 stars⑂ 0 forkssince May 2019View on GitHub ↗
KindLibraryDesktop applicationhow this is determined

WildGums/Orc.DataAccess holds a health index of 30 out of 100, placing it in the At Risk band. It scores highest on Vitality (88/100) and lowest on Engineering Quality (30/100). It was last updated today. A single contributor accounts for most of its recent work.

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

30
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 57 is calibrated to 60 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 50% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

WildGumsOrganization
43 followers64 public repossince Jan 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
NuGetOrc.DataAccess6.0.0-130 days agoorcdataaccess
NuGetOrc.DataAccess.Xaml6.0.0-150 days agoorcdataaccessxaml

Metrics by category

Vitality

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

88Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
35.3/36Commit cadence51/52 weeks with commits
18/18Commit volume391 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year391
human_commit_share0.7
days_since_last_push0
active_weeks_last_year51
How it's scored
16.2/27Ships releases18 version tags (no GitHub releases)
36/36Release recencylatest release 0 days ago
12.6/27Release cadencea release every ~179.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count18
latest_release_tag6.0.0
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases179.3
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?

42Weak · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
3.9/15Watchers6 watchers
Inputs used
forks0
stars0
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
51.1/80Total downloads82,122 downloads all-time across nuget
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesOrc.DataAccess, Orc.DataAccess.Xaml
dependents
ecosystemsnuget
total_downloads82,122
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?

70Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.3/22.5Commit distributiontop contributor authored 85% of commits
6.8/13.5Contributor breadth5 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.854
How it's scored
42/42Issue resolution100% of issues closed
27.6/30PR acceptance965/1,048 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/7 approved changesets -- score normalized to 0
Inputs used
merged_prs965
open_issues0
closed_issues3
prs_merged_7d5
prs_decided_7d5
prs_merged_30d5
prs_decided_30d5
issue_closed_ratio1
closed_unmerged_prs83
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 backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
11.8/25Owner reach43 followers of WildGums
25/25Track record64 public repos, account ~11 yr old
Inputs used
followers43
owner_typeOrganization
is_verified
owner_loginWildGums
public_repos64
account_age_days4,238
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on nuget
35/35Publish recencylatest publish 0 days ago
20/20Version history15 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesOrc.DataAccess, Orc.DataAccess.Xaml
ecosystemsnuget
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

30At Risk · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 15 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

30At Risk
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

46Weak · 16% of overall
How it's scored
6/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 15 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 0/7 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 4 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
5/5Pinned-Dependenciesall dependencies are pinned
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
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.6
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier50
security_posture_after_multiplier33
security_posture_before_jurisdiction66
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 50% multiplier and gives Security posture an At risk ceiling of 34.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages17
unassessed_packages3
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 17 resolved dependencies against OSV. 3 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

66Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
37.3/40Legible commit history49 of 70 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.7
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes5,787
How it's scored
12.6/18One-command bootstrapsrc/Orc.DataAccess.Example/Orc.DataAccess.Example.csproj, src/Orc.DataAccess.Tests/Orc.DataAccess.Tests.csproj, src/Orc.DataAccess.Xaml/Orc.DataAccess.Xaml.csproj (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checkingC# (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance30 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestssrc/Orc.DataAccess.Example/Orc.DataAccess.Example.csproj, src/Orc.DataAccess.Tests/Orc.DataAccess.Tests.csproj, src/Orc.DataAccess.Xaml/Orc.DataAccess.Xaml.csproj, src/Orc.DataAccess/Orc.DataAccess.csproj
dependency_bot_commit_share0.3
How it's scored
45/45Type-checkable codeC# (statically typed)
55/55Manageable file sizes0/144 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes12,514
source_files_sampled144
oversized_source_files0

Key facts

0GitHub stars
5contributors
391commits, last 12 months
0days since last push
18releases
1bus factor
0open issues
package ecosystems

Data collection warnings

  • Could not fetch nuget package 'Orc.DataAccess.Tests' from its registry

More detail

OpenSSF Scorecard 6.6 / 10
6.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-08-21 12:50 UTC

8Binary-Artifactsbinaries present in source code
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
0CI-Tests0 out of 15 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 0/7 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 32
RegistryPackageVersion constraintManifest
NuGetCatel.Fody7.1.0src/Orc.DataAccess.Example/Orc.DataAccess.Example.csproj
NuGetCatel.SourceGenerators7.1.0src/Orc.DataAccess.Example/Orc.DataAccess.Example.csproj
NuGetFody6.9.3src/Orc.DataAccess.Example/Orc.DataAccess.Example.csproj
NuGetMicrosoft.Extensions.Hosting10.0.*src/Orc.DataAccess.Example/Orc.DataAccess.Example.csproj
NuGetMicrosoft.Extensions.Logging.Debug10.0.*src/Orc.DataAccess.Example/Orc.DataAccess.Example.csproj
NuGetMicrosoft.Extensions.Logging.Console10.0.*src/Orc.DataAccess.Example/Orc.DataAccess.Example.csproj
NuGetOrchestra.Core8.0.0-alpha0321src/Orc.DataAccess.Example/Orc.DataAccess.Example.csproj
NuGetCatel.Fody7.1.0src/Orc.DataAccess.Tests/Orc.DataAccess.Tests.csproj
NuGetFody6.9.3src/Orc.DataAccess.Tests/Orc.DataAccess.Tests.csproj
NuGetMicrosoft.Extensions.Logging.Console10.0.*src/Orc.DataAccess.Tests/Orc.DataAccess.Tests.csproj
NuGetMicrosoft.Extensions.Logging.Debug10.0.*src/Orc.DataAccess.Tests/Orc.DataAccess.Tests.csproj
NuGetMicrosoft.NET.Test.Sdk18.9.0src/Orc.DataAccess.Tests/Orc.DataAccess.Tests.csproj
NuGetMoq4.20.72src/Orc.DataAccess.Tests/Orc.DataAccess.Tests.csproj
NuGetNUnit4.6.1src/Orc.DataAccess.Tests/Orc.DataAccess.Tests.csproj
NuGetNUnit3TestAdapter6.2.0src/Orc.DataAccess.Tests/Orc.DataAccess.Tests.csproj
NuGetOrc.Automation.Tests6.0.1src/Orc.DataAccess.Tests/Orc.DataAccess.Tests.csproj
NuGetPublicApiGenerator11.5.4src/Orc.DataAccess.Tests/Orc.DataAccess.Tests.csproj
NuGetVerify.NUnit31.28.0src/Orc.DataAccess.Tests/Orc.DataAccess.Tests.csproj
NuGetCatel.Fody7.1.0src/Orc.DataAccess.Xaml/Orc.DataAccess.Xaml.csproj
NuGetCatel.SourceGenerators7.1.0src/Orc.DataAccess.Xaml/Orc.DataAccess.Xaml.csproj
NuGetFody6.9.3src/Orc.DataAccess.Xaml/Orc.DataAccess.Xaml.csproj
NuGetMethodTimer.Fody3.2.3src/Orc.DataAccess.Xaml/Orc.DataAccess.Xaml.csproj
NuGetMicrosoft.Data.SqlClient7.0.2src/Orc.DataAccess.Xaml/Orc.DataAccess.Xaml.csproj
NuGetObsolete.Fody5.3.1src/Orc.DataAccess.Xaml/Orc.DataAccess.Xaml.csproj
NuGetOrc.Controls6.0.0src/Orc.DataAccess.Xaml/Orc.DataAccess.Xaml.csproj
NuGetCatel.Fody7.1.0src/Orc.DataAccess/Orc.DataAccess.csproj
NuGetCatel.SourceGenerators7.1.0src/Orc.DataAccess/Orc.DataAccess.csproj
NuGetExcelDataReader.DataSet3.9.0src/Orc.DataAccess/Orc.DataAccess.csproj
NuGetFody6.9.3src/Orc.DataAccess/Orc.DataAccess.csproj
NuGetMethodTimer.Fody3.2.3src/Orc.DataAccess/Orc.DataAccess.csproj
NuGetObsolete.Fody5.3.1src/Orc.DataAccess/Orc.DataAccess.csproj
NuGetOrc.Csv6.0.0src/Orc.DataAccess/Orc.DataAccess.csproj
All dependencies 20

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

RegistryPackageVersionRelation
NuGetCatel.Fody7.1.0direct
NuGetCatel.SourceGenerators7.1.0direct
NuGetExcelDataReader.DataSet3.9.0direct
NuGetFody6.9.3direct
NuGetMethodTimer.Fody3.2.3direct
NuGetMicrosoft.Data.SqlClient7.0.2direct
NuGetMicrosoft.Extensions.Hostingdirect
NuGetMicrosoft.Extensions.Logging.Consoledirect
NuGetMicrosoft.Extensions.Logging.Debugdirect
NuGetMicrosoft.NET.Test.Sdk18.9.0direct
NuGetMoq4.20.72direct
NuGetNUnit4.6.1direct
NuGetNUnit3TestAdapter6.2.0direct
NuGetObsolete.Fody5.3.1direct
NuGetOrc.Automation.Tests6.0.1direct
NuGetOrc.Controls6.0.0direct
NuGetOrc.Csv6.0.0direct
NuGetOrchestra.Core8.0.0-alpha0321direct
NuGetPublicApiGenerator11.5.4direct
NuGetVerify.NUnit31.28.0direct
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 17 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 3 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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