Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 14:12 UTC

argentsea / sql

The Argent Sea framework for SQL Server

C#Custom license★ 2 stars⑂ 0 forkssince Mar 2018View on GitHub ↗

argentsea/sql holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (48/100) and lowest on Security (21/100). It was last updated 6 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

ArgentSeaOrganization
0 followers9 public repossince May 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
NuGetArgentSea.Sql2.0.3-162 days ago

Metrics by category

Vitality

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

47Weak · 21% of overall
How it's scored
36/36Push recency — last push 6 days ago
2.1/36Commit cadence — 3/52 weeks with commits
7.6/18Commit volume — 6 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year6
human_commit_share1
days_since_last_push6
active_weeks_last_year3
How it's scored
16.2/27Ships releases — 14 version tags (no GitHub releases)
0/36Release recency — latest release 2,104 days ago
19.8/27Release cadence — a release every ~65.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count14
latest_release_tag1.0.0
releases_from_tagsyes
days_since_latest_release2,104
mean_days_between_releases65.5

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

30At Risk · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars2
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesdev.azure.com
has_pull_request_templateno
How it's scored
46.8/80Total downloads — 31,707 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesArgentSea.Sql
dependents—
ecosystemsnuget
total_downloads31,707
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?

48Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
0/25Owner reach — 0 followers of argentsea
19.3/25Track record — 9 public repos, account ~9 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_loginargentsea
public_repos9
account_age_days3,421

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

42Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
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/10Topics — 11 topics
10/10Wiki
Inputs used
topicsado-net, sql-server, sqlserver, database, sharding, shard, orm, orm-library, orm-framework, data-library, netstandard
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?

21At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestssrc/ArgentSea.Sql.csproj, test/ArgentSea.Sql.Test.csproj
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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_packages14
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 14 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.

41Weak · 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 77 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 — src/ArgentSea.Sql.csproj, test/ArgentSea.Sql.Test.csproj (toolchain convention, no task runner)
22/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 77
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestssrc/ArgentSea.Sql.csproj, test/ArgentSea.Sql.Test.csproj
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — C# (statically typed)
47.5/55Manageable file sizes — 3/22 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes125,811
source_files_sampled22
oversized_source_files3

Key facts

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

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/argentsea/sql: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-09-15T14:12:25Z. Please include `DD12:22D7EC:A7BA6FA:A3A5A6F:6AA95248` when reporting this issue.); skipping Scorecard checks

More detail

Direct dependencies 2
RegistryPackageVersion constraintManifest
NuGetMicrosoft.Data.SqlClient6.0.1src/ArgentSea.Sql.csproj
NuGetMicrosoft.Extensions.Logging9.0.2src/ArgentSea.Sql.csproj
All dependencies 14

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

RegistryPackageVersionRelation
NuGetMicrosoft.Data.SqlClient6.0.1direct
NuGetMicrosoft.Extensions.Logging9.0.2direct
NuGetFluentAssertions6.12.1indirect
NuGetMicrosoft.CodeCoverage17.13.0indirect
NuGetMicrosoft.Extensions.Configuration9.0.2indirect
NuGetMicrosoft.Extensions.Configuration.Json9.0.2indirect
NuGetMicrosoft.Extensions.DependencyInjection9.0.2indirect
NuGetMicrosoft.Extensions.Logging.Console9.0.2indirect
NuGetMicrosoft.Extensions.Options.ConfigurationExtensions9.0.2indirect
NuGetMicrosoft.NET.Test.Sdk17.13.0indirect
NuGetNSubstitute5.3.0indirect
NuGetxunit2.9.3indirect
NuGetxunit.analyzers1.20.0indirect
NuGetxunit.runner.visualstudio3.0.2indirect
Dependency advisories 0

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