Leaderboard github.com
ThatRendle/Simple.Data
A light-weight, dynamic data access component for C# 4.0
AI provenance
0%
none-detected
- Confidence
- 65%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
66/100
adequate
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
73/100
adequate
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
AI provenance
0% none-detected
No AI attribution or AI-consistent velocity signals detected.
How the score is built
- Explicitly attributed share0%
- Unattributed share in AI-pace bursts0%
- Estimated AI-generated share0%
- AI tool configuration files0
- Work sessions at AI pace0
- Releases at AI pace0
- Coding-style index (1.0+ means possible)0.00
Lines added per month all AI-attributed share
- 2010-0814,956 · 0% AI
- 2010-091,105 · 0% AI
- 2010-105,893 · 0% AI
- 2010-1110,731 · 0% AI
- 2010-12918 · 0% AI
- 2011-013,318 · 0% AI
- 2011-021,198 · 0% AI
- 2011-031,240 · 0% AI
- 2011-043,059 · 0% AI
- 2011-052,707 · 0% AI
- 2011-061,367 · 0% AI
- 2011-077,044 · 0% AI
- 2011-083,342 · 0% AI
- 2011-091,313 · 0% AI
- 2011-108,812 · 0% AI
- 2011-113,691 · 0% AI
- 2011-12594 · 0% AI
- 2012-011,954 · 0% AI
- 2012-022,724 · 0% AI
- 2012-031,603 · 0% AI
- 2012-0485 · 0% AI
- 2012-051,081 · 0% AI
- 2012-06119 · 0% AI
- 2012-07400 · 0% AI
- 2012-081,153 · 0% AI
- 2012-09193 · 0% AI
- 2012-10171 · 0% AI
- 2012-11888 · 0% AI
- 2012-12501 · 0% AI
- 2013-01483 · 0% AI
- 2013-0280 · 0% AI
- 2013-04528 · 0% AI
- 2013-05353 · 0% AI
- 2013-061 · 0% AI
- 2013-0818 · 0% AI
- 2013-0932 · 0% AI
- 2013-117 · 0% AI
- 2013-12122 · 0% AI
- 2014-0160 · 0% AI
- 2014-03118 · 0% AI
Evidence by analyzer
Explicit AI attributionok
- attributed_commit_share
- 0.0%
- attributed_commits
- 0
- attributed_loc
- 0
- attributed_loc_share
- 0.0%
- commits
- 632
- effective_loc
- 83,962
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 19,715
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 823.11
- measured_loc
- 63,092
- median_loc_per_hour
- 70.47
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 3,364
- pre_ai_era_bursts
- 1
- pre_ai_era_measured_loc
- 63,092
- work_units
- 415
Release velocityok
- flagged_releases
- 0
- max_loc_per_day
- 160.20
- releases
- 20
Coding styleok
- count:assistant_voice
- 0
- count:emoji_in_code
- 0
- count:narrated_steps
- 0
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 0
- files:narrated_steps
- 0
- files:placeholder
- 0
- index
- 0
- lines_scanned
- 35,024
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0
- per_kloc:placeholder
- 0
Code quality
66 adequate
Code quality is adequate: test-to-source ratio 0.10, no CI test run detected; 0% of function code in complex or long functions; 14% duplicated lines. Weakest area: testing.
How the score is built
- Complexity99
- Duplication43
- Lint and smells100
- Tests and CI35
- Documentation65
- Type safetynot measured
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok1 item
- complex_functions
- 1
- function_nloc
- 19,972
- functions
- 2,622
- long_functions
- 0
- many_param_functions
- 0
- mean_ccn
- 1.57
- p90_ccn
- 3
- risky_nloc_share
- 0.5%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: CommonAssemblyInfo.cs:14 and PerformanceTestConsole/Properties/AssemblyInfo.cs:14
- 6+ duplicated lines: PerformanceTestConsole/Properties/AssemblyInfo.cs:13 and ProfilingApp/Properties/AssemblyInfo.cs:13
- 6+ duplicated lines: ProfilingApp/Properties/Resources.Designer.cs:1 and ProfilingApp/Properties/Settings.Designer.cs:1
- 6+ duplicated lines: ProfilingApp/Properties/Resources.Designer.cs:15 and Simple.Data.SqlCe35/Properties/Resources.Designer.cs:15
- 6+ duplicated lines: ProfilingApp/Properties/Settings.Designer.cs:14 and Simple.Data.Ado/Properties/Settings.Designer.cs:14
- 6+ duplicated lines: ProfilingApp/Properties/Settings.Designer.cs:20 and Simple.Data.SqlTest/Properties/Settings.Designer.cs:20
- 6+ duplicated lines: Simple.Data.AdapterApi/Properties/AssemblyInfo.cs:13 and Simple.Data.BehaviourTest/Properties/AssemblyInfo.cs:13
- 6+ duplicated lines: Simple.Data.Ado.Test/ConnectionModifierTest.cs:58 and Simple.Data.Ado.Test/ConnectionModifierTest.cs:108
- 6+ duplicated lines: Simple.Data.Ado.Test/ProviderHelperTest.cs:73 and Simple.Data.Ado.Test/TestCustomInserter.cs:48
- 6+ duplicated lines: Simple.Data.Ado/AdoAdapter.IAdapterWithRelation.cs:8 and Simple.Data.Mocking/XmlMockAdapter.cs:151
- compared_lines
- 19,089
- duplicated_lines
- 2,658
- duplicated_share
- 13.9%
- files
- 424
Lintok
- findings
- 0
- scanned_lines
- 34,992
- weighted_findings
- 0
Tests and CIok
- check:ci_present
- no
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- yes
- check:test_ratio
- no
- check:tests_cochange
- yes
- ci_files
- 0
- cochange_commits
- 262
- cochange_share
- 26.7%
- source_lines
- 35,024
- test_lines
- 3,393
- test_ratio
- 0.10
Documentationok2 items
- README.md
README.md - LICENSE.txt
LICENSE.txt
- check:changelog
- no
- check:contributing
- no
- check:license
- yes
- check:readme
- yes
- readme_lines
- 58
Type safetyskipped
Security
73 adequate
Security posture is adequate: 13 high-severity SAST findings. Weakest area: posture.
How the score is built
- Secrets97
- Static analysis (SAST)79
- Vulnerable dependenciesnot measured
- CI workflowsnot measured
- Security posture0
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesskipped
no registry dependencies declared
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 0
- secrets_nonprod
- 1
Static analysis (opengrep)ok
- findings
- 13
- findings_high
- 13
- findings_low
- 0
- findings_medium
- 0
- parse_errors
- 0
- scanned_lines
- 34,992
- weighted_findings
- 23.40
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok
- check:dependency_updates
- no
- check:lockfiles
- yes
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 0.0%
- unpinned_manifests
- 0
Release downloadsok1 item
- gives an archive password
README.md
- binary_assets
- 0
- signals
- 1
- suspicious
- 0
Findings
13 high1 low
14 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Simple.Data.Ado/AdoAdapterInserter.cs:132 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Simple.Data.Ado/AdoAdapterInserter.cs:144 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Simple.Data.Ado/BulkInserterHelper.cs:53 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Simple.Data.Ado/BulkInserterTransactionHelper.cs:23 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Simple.Data.Ado/CommandBuilder.cs:109 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Simple.Data.Ado/CommandBuilder.cs:121 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Simple.Data.Ado/CommandBuilder.cs:266 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Simple.Data.Ado/CommandBuilder.cs:271 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Simple.Data.Ado/CommandHelper.cs:126 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Simple.Data.Ado/CommandHelper.cs:134 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Simple.Data.Ado/CommandHelper.cs:144 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Simple.Data.Ado/CommandHelper.cs:28 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli |
Simple.Data.Ado/CommandTemplate.cs:35 | Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and... | Static analysis (opengrep) |
| low | gitleaks/generic-api-key |
Simple.Data.Mocking.Test/XmlMockAdapterTest.cs:25 | Possible generic-api-key secret in the current tree (test/docs/example file) | Secrets (gitleaks) |
Tools and coverage
Every analyzer that ran on this commit. A failed or skipped tool is a coverage gap: its share of the score is left out and the coverage figure drops.
| Analyzer | Pillar | Status | Version | Findings | Note |
|---|---|---|---|---|---|
| AI tool configuration | AI provenance | ok | signatures-v1 | 0 | |
| Explicit AI attribution | AI provenance | ok | signatures-v1 | 0 | |
| Release velocity | AI provenance | ok | prov-4 | 0 | |
| Coding style | AI provenance | ok | — | 0 | |
| Commit velocity | AI provenance | ok | prov-4 | 0 | |
| Complexity (lizard) | Code quality | ok | lizard 1.25.1 | 0 | |
| Documentation | Code quality | ok | — | 0 | |
| Duplication (jscpd) | Code quality | ok | repotrust-dup-w6 | 0 | |
| Lint | Code quality | ok | opengrep 1.33.1; rules f1d2b562b414 | 0 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | skipped | — | 0 | |
| CI workflows (zizmor) | Security | skipped | — | 0 | |
| Dependencies (osv-scanner) | Security | skipped | — | 0 | |
| Release downloads | Security | ok | — | 0 | |
| Security posture | Security | ok | — | 0 | |
| Package registries | Security | skipped | — | 0 | no registry dependencies declared |
| Static analysis (opengrep) | Security | ok | opengrep 1.33.1; rules f1d2b562b414 | 13 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 1 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | 65ff01e482ce | prov-5+qual-2+sec-2 | 0% | 66 | 73 |
| 2026-11-14 | 65ff01e482ce | prov-4+qual-2+sec-2 | 0% | 66 | 73 |
Full text report
- Repository: https://github.com/ThatRendle/Simple.Data
- Commit:
65ff01e482ce71190869001c221caa140feb70e5 - Generated: 2026-11-14T14:52:01+00:00
- Scorer 0.1.0, scoring prov-5+qual-2+sec-2, report schema v2
Scores
| Pillar | Score | Signal | Confidence | Coverage |
|---|---|---|---|---|
| AI provenance (estimated AI-generated share) | 0 | none-detected | 65% | 100% |
| Code quality | 66 | adequate | 90% | 100% |
| Security | 73 | adequate | 85% | 100% |
AI provenance
No AI attribution or AI-consistent velocity signals detected.
- Explicitly attributed share (lower bound): 0.0%
- Unattributed share in AI-consistent velocity bursts: 0.0%
- Estimated AI-generated share: 0.0%
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2012-12 | 501 | 0% |
| 2013-01 | 483 | 0% |
| 2013-02 | 80 | 0% |
| 2013-04 | 528 | 0% |
| 2013-05 | 353 | 0% |
| 2013-06 | 1 | 0% |
| 2013-08 | 18 | 0% |
| 2013-09 | 32 | 0% |
| 2013-11 | 7 | 0% |
| 2013-12 | 122 | 0% |
| 2014-01 | 60 | 0% |
| 2014-03 | 118 | 0% |
AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.
Code quality
Code quality is adequate: test-to-source ratio 0.10, no CI test run detected; 0% of function code in complex or long functions; 14% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 99 |
| Duplication | 43 |
| Code smells (Opengrep) | 100 |
| Tests and CI | 35 |
| Documentation | 65 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 2,622; mean complexity 1.6, 90th percentile 3; 1 complex and 0 long functions
- Duplicated lines: 13.9% of 19,089 compared
- Tests: 3,393 test lines for 35,024 source lines (ratio 0.10); CI test commands: none detected; 27% of recent source commits also change tests
- Docs missing or thin: contributing, changelog
Most complex functions:
Security
Security posture is adequate: 13 high-severity SAST findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 97 |
| Static analysis (Opengrep) | 79 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
- Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Simple.Data.Ado/AdoAdapterInserter.cs:132 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Simple.Data.Ado/AdoAdapterInserter.cs:144 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Simple.Data.Ado/BulkInserterHelper.cs:53 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Simple.Data.Ado/BulkInserterTransactionHelper.cs:23 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Simple.Data.Ado/CommandBuilder.cs:109 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Simple.Data.Ado/CommandBuilder.cs:121 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Simple.Data.Ado/CommandBuilder.cs:266 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Simple.Data.Ado/CommandBuilder.cs:271 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Simple.Data.Ado/CommandHelper.cs:28 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Simple.Data.Ado/CommandHelper.cs:126 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Simple.Data.Ado/CommandHelper.cs:134 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Simple.Data.Ado/CommandHelper.cs:144 |
| high | opengrep/csharp.lang.security.sqli.csharp-sqli: Detected a formatted string in a SQL statement. This could lead to SQL injection if variables in the SQL statement are not properly sanitized. Use a prepared statements instead. You can obtain a PreparedStatement using 'SqlCommand' and 'SqlParameter'. [confidence medium] |
Simple.Data.Ado/CommandTemplate.cs:35 |
| low | gitleaks/generic-api-key: Possible generic-api-key secret in the current tree (test/docs/example file) |
Simple.Data.Mocking.Test/XmlMockAdapterTest.cs:25 |
Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.
Distribution signals
- readme-download-lure: gives an archive password
Signals consistent with a repository that exists to distribute a download. They are heuristics, not a verdict; release files were not downloaded or inspected.
Repository profile
- Source lines: 35,024; test lines: 3,393
| Language | Lines |
|---|---|
| C# | 38,383 |
| PowerShell | 32 |
| Shell | 2 |