Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 10:15 UTC

re-motion / Relinq-SqlBackend

C# · TSQLCustom license★ 26 stars⑂ 11 forkssince Sep 2014View on GitHub ↗

re-motion/Relinq-SqlBackend holds a health index of 36 out of 100, placing it in the Weak band. It scores highest on Vitality (58/100) and lowest on Engineering Quality (11/100). It was last updated 34 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

re-motionOrganization
10 followers39 public repossince May 2014

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

Metrics by category

Vitality

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

58Moderate · 21% of overall
How it's scored
18/36Push recencylast push 34 days ago
3.5/36Commit cadence5/52 weeks with commits
12.1/18Commit volume21 commits in the last year
10/10OpenSSF Scorecard: Maintained15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year21
human_commit_share1
days_since_last_push34
active_weeks_last_year5
How it's scored
16.2/27Ships releases50 version tags (no GitHub releases)
36/36Release recencylatest release 34 days ago
19.8/27Release cadencea release every ~90.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count50
latest_release_tagv4.0.0
releases_from_tagsyes
days_since_latest_release34
mean_days_between_releases90.1
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?

27At Risk · 17% of overall
How it's scored
22.7/60Stars26 stars
8.3/25Forks11 forks
2.7/15Watchers4 watchers
Inputs used
forks11
stars26
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
16.9/22.5Licenselicense 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_readmeno
has_licenseno
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

53Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.5/22.5Commit distributiontop contributor authored 85% of commits
13.5/13.5Contributor breadth12 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled12
top_contributor_share0.846
How it's scored
0/42Issue resolutionno issues or no data
25.6/30PR acceptance41/48 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 4/20 approved changesets -- score normalized to 2
Inputs used
merged_prs41
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs7
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 backingorganization-owned
0/20Verified domain
7.5/25Owner reach10 followers of re-motion
23.7/25Track record39 public repos, account ~12 yr old
Inputs used
followers10
owner_typeOrganization
is_verifiedno
owner_loginre-motion
public_repos39
account_age_days4,501

Engineering Quality

Are baseline engineering and documentation practices in place?

11Critical · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

25At Risk
How it's scored
0/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://www.re-motion.org/jira/browse/RMLNQSQL
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepagehttps://www.re-motion.org/jira/browse/RMLNQSQL
docs_sitehttps://www.re-motion.org/jira/browse/RMLNQSQL
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

55Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Tests0 out of 4 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
1.5/7.5Code-ReviewFound 4/20 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 4 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
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
0/7.5Token-Permissionsno data
6/7.5Vulnerabilities2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

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
advisories2
affected_packages2
assessed_packages25
unassessed_packages8
affected_by_severityhigh 1, moderate 1
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 25 resolved dependencies against OSV. 8 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.

34At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
10.7/40Legible commit history20 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.2
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapBuild/Build.csproj, Core/Core.csproj, Development/Development.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
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsBuild/Build.csproj, Core/Core.csproj, Development/Development.csproj, IntegrationTests.CSharp/IntegrationTests.CSharp.csproj, IntegrationTests.Common/IntegrationTests.Common.csproj, IntegrationTests.MediumTrust/IntegrationTests.MediumTrust.csproj, LinqToSqlAdapter.UnitTests/LinqToSqlAdapter.UnitTests.csproj, LinqToSqlAdapter/LinqToSqlAdapter.csproj, UnitTests/UnitTests.csproj
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeC# (statically typed)
54.8/55Manageable file sizes3/668 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes211,852
source_files_sampled668
oversized_source_files3

Key facts

26GitHub stars
12contributors
21commits, last 12 months
34days since last push
50releases
1bus factor
0open issues
NuGetpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 11 ⇿
0Stars
11Forks
16Releases

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.

02468101012015-022019-082024-02
Major 1Minor 2Patch 2

Each point covers 9 days.

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-17 10:15 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 4 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 4/20 approved changesets -- score normalized to 2
10Contributorsproject has 4 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 21
RegistryPackageVersion constraintManifest
NuGetRemotion.LinqCore/Core.csproj
NuGetRemotion.LinqDevelopment/Development.csproj
NuGetRemotion.Linq.DevelopmentDevelopment/Development.csproj
NuGetRemotion.LinqIntegrationTests.Common/IntegrationTests.Common.csproj
NuGetMicrosoft.Data.SqlClientIntegrationTests.Common/IntegrationTests.Common.csproj
NuGetCore.Data.LinqIntegrationTests.Common/IntegrationTests.Common.csproj
NuGetSystem.Configuration.ConfigurationManagerIntegrationTests.Common/IntegrationTests.Common.csproj
NuGetCore.Data.LinqIntegrationTests.Common/IntegrationTests.Common.csproj
NuGetSystem.Configuration.ConfigurationManagerIntegrationTests.Common/IntegrationTests.Common.csproj
NuGetCore.Data.LinqIntegrationTests.Common/IntegrationTests.Common.csproj
NuGetSystem.Configuration.ConfigurationManagerIntegrationTests.Common/IntegrationTests.Common.csproj
NuGetCore.Data.LinqIntegrationTests.Common/IntegrationTests.Common.csproj
NuGetSystem.Configuration.ConfigurationManagerIntegrationTests.Common/IntegrationTests.Common.csproj
NuGetCore.Data.LinqIntegrationTests.Common/IntegrationTests.Common.csproj
NuGetSystem.Configuration.ConfigurationManagerIntegrationTests.Common/IntegrationTests.Common.csproj
NuGetMicrosoft.Data.SqlClientIntegrationTests.MediumTrust/IntegrationTests.MediumTrust.csproj
NuGetNUNitIntegrationTests.MediumTrust/IntegrationTests.MediumTrust.csproj
NuGetNUnitTestAdapterIntegrationTests.MediumTrust/IntegrationTests.MediumTrust.csproj
NuGetRemotion.LinqLinqToSqlAdapter/LinqToSqlAdapter.csproj
NuGetCore.Data.LinqLinqToSqlAdapter/LinqToSqlAdapter.csproj
NuGetMicrosoft.VisualBasicUnitTests/UnitTests.csproj
All dependencies 33

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

RegistryPackageVersionRelation
NuGetCore.Data.Linqdirect
NuGetMicrosoft.Data.SqlClientdirect
NuGetMicrosoft.VisualBasicdirect
NuGetNUnitdirect
NuGetNUnitTestAdapterdirect
NuGetRemotion.Linqdirect
NuGetRemotion.Linq.Developmentdirect
NuGetSystem.Configuration.ConfigurationManagerdirect
NuGetSystem.Configuration.ConfigurationManager4.7.0direct
NuGetDependDB.BuildProcessor1.8.1indirect
NuGetDependDB.BuildProcessor2.0.0indirect
NuGetDependDB.BuildProcessor.NuGetPreProcessor1.8.1indirect
NuGetDependDB.BuildProcessor.NuGetPreProcessor2.0.0indirect
NuGetJetBrains.Annotations2019.1.3indirect
NuGetMicrosoft.Build.Framework17.2.0indirect
NuGetMicrosoft.Build.Utilities.Core17.2.0indirect
NuGetMicrosoft.IO.Redist6.0.0indirect
NuGetMicrosoft.NET.StringTools1.0.0indirect
NuGetNuGet.CommandLine3.5.0indirect
NuGetNuGet.for.MSBuild1.4.3indirect
NuGetNUnit.ConsoleRunner3.15.5indirect
NuGetNUnit.Extension.NUnitV2Driver3.8.0indirect
NuGetNUnit.Runners2.6.3indirect
NuGetRemotion.BuildScript3.0.0-alpha.6indirect
NuGetRemotion.BuildTools.MSBuildTasks1.0.6180.28602indirect
NuGetSystem.Buffers4.5.1indirect
NuGetSystem.Collections.Immutable5.0.0indirect
NuGetSystem.Memory4.5.4indirect
NuGetSystem.Numerics.Vectors4.5.0indirect
NuGetSystem.Runtime.CompilerServices.Unsafe6.0.0indirect
NuGetSystem.Security.AccessControl4.7.0indirect
NuGetSystem.Security.Permissions4.7.0indirect
NuGetSystem.Security.Principal.Windows4.7.0indirect
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
Microsoft.IO.Redist6.0.0indirecthigh16.0.1
NuGet.CommandLine3.5.0indirectmoderate16.2.1

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.