Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
40 of your 87 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 147.18s for a 117.4 MB repo slow.
  • Repobility's analysis ran in 7.96s after the clone landed.

dolthub/doltlite

https://github.com/dolthub/doltlite · scanned 2026-06-05 19:13 UTC (4 days, 16 hours ago) · 10 languages

233 raw signals (81 security + 152 graph) 11/13 scanners ran 100th percentile · C · huge (>500K LoC)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 16 hours ago · v2 · 76 actionable findings from 2 signal sources. 81 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 65.0 0.15 9.75
security_score 100.0 0.25 25.00
testing_score 80.0 0.20 16.00
documentation_score 89.0 0.15 13.35
practices_score 70.0 0.15 10.50
code_quality 50.0 0.10 5.00
Overall 1.00 79.6
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Scan summary Quality grade B+ (80/100). Dimensions: security 100, maintainability 65. 81 findings (29 security). 562,121 lines analyzed.

Showing 50 of 76 actionable findings. 157 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high Security checks security path traversal conf 0.80 [SEC013] Path Traversal — User Input in File Path: User-controlled input used in file path without sanitization. Allows reading arbitrary files.
Use os.path.realpath() and verify the path starts with your expected base directory. Use secure_filename() for uploads.
tool/dbtotxt.c:117
low Security checks cicd CI/CD security conf 0.90 ✓ Repobility 39 occurrences GitHub Action is tag-pinned rather than SHA-pinned
[MINED115] Action `actions/checkout` pinned to mutable ref `@v4`: `uses: actions/checkout@v4` resolves at workflow-run time. Tags and branches can be re-pushed by the action owner; that made the tj-actions/changed-files compromise (2025) instantly affect ~23K repos. Pin to a 40-char commit SHA + lo…
7 files, 39 locations
.github/workflows/release.yml:19, 22, 41, 107, 151, 269, 299, 374, +3 more (18 hits)
.github/workflows/benchmark.yml:20, 64, 142, 183 (6 hits)
.github/workflows/build-test.yml:16, 19, 38, 93, 397 (5 hits)
.github/workflows/test.yml:12, 41, 84, 146 (4 hits)
.github/workflows/smoke.yml:15, 162 (3 hits)
.github/workflows/sqlite-upstream-drift.yml:28 (2 hits)
.github/workflows/sanitizers.yml:12
CI/CD securitySupply chainGitHub Actions
high System graph security security conf 1.00 Insecure pattern 'exec_used' in ext/wasm/api/sqlite3-api-glue.c-pp.js:175
Found a known-risky pattern (exec_used). Review and replace if possible.
ext/wasm/api/sqlite3-api-glue.c-pp.js:175 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in ext/wasm/demo-worker1-promiser.c-pp.js:187
Found a known-risky pattern (exec_used). Review and replace if possible.
ext/wasm/demo-worker1-promiser.c-pp.js:187 Exec used
medium Security checks quality Quality Average file size is 937 lines (recommend <300)
Refactor large files by extracting related functions into separate modules. Target files with 300+ lines first. Use the Single Responsibility Principle — each module should have one clear purpose.
high Security checks quality Quality conf 0.82 Parallel implementation file sits beside a canonical file
Merge the intended change into the canonical file, update tests/imports, and delete the parallel implementation if it is not the active entry point.
ext/jni/src/org/sqlite/jni/capi/sqlite3_backup.java:1
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ext/wasm/api/pre-js.c-pp.js:119
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — ext/wasm/common/whwasmutil.js:2502
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
msys2/setup-msys2@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 3 locations
.github/workflows/release.yml:170 (2 hits)
.github/workflows/build-test.yml:124
CI/CD securitySupply chainGitHub Actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). Either auth lives in custom code, in a separate service, or is missing.
auth
low Security checks quality Error handling conf 1.00 [ERR003] Ignored Error (Go): Ignoring error return values.
Handle the error or use errcheck linter.
examples/go/main.go:92
low Security checks quality Quality conf 0.60 30 occurrences Duplicated implementation block across source files
Duplicate implementation blocks are maintenance debt. Keep them visible, but they are not a high-severity defect unless the duplicated logic is security-sensitive or drifting.
12 files, 20 locations
ext/fts5/fts5_test_tok.c:27, 45, 294 (3 hits)
ext/misc/unionvtab.c:70, 72, 786 (3 hits)
ext/blake3/blake3_sse41.c:1, 212 (2 hits)
ext/misc/csv.c:618, 650 (2 hits)
ext/misc/fuzzer.c:186, 704 (2 hits)
ext/misc/series.c:491, 493 (2 hits)
ext/blake3/blake3_portable.c:112
ext/blake3/blake3_sse2.c:217
duplicationquality
low System graph software Dead code candidate conf 1.00 File has no detected symbols: ext/wasm/api/extern-pre-js.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: ext/wasm/api/sqlite3-license-version-header.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: ext/wasm/api/sqlite3-worker1.c-pp.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: ext/wasm/demo-jsstorage.js
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: test/tools/chunk_physical_dups.py:read_manifest, test/tools/chunk_size_dist.py:read_manifest This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separa…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `sqlite3_close_v2` in ext/wasm/api/sqlite3-api-glue.c-pp.js:113
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `sqlite3_create_function_v2` in ext/wasm/api/sqlite3-api-prologue.js:519
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `sqlite3_open_v2` in ext/wasm/api/sqlite3-vfs-opfs-sahpool.c-pp.js:120
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `sqlite3_prepare_v2` in ext/wasm/common/whwasmutil.js:2208
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `sqlite3_prepare_v2` in ext/wasm/tester1.c-pp.js:1438
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `sqlite3_trace_v2` in ext/wasm/api/sqlite3-api-oo1.c-pp.js:98
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — ext/wasm/api/sqlite3-api-oo1.c-pp.js:105
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — ext/wasm/api/sqlite3-worker1-promiser.c-pp.js:99
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — ext/wasm/common/SqliteTestUtil.js:175
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — ext/wasm/demo-123.js:24
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — ext/wasm/demo-jsstorage.js:79
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — ext/wasm/demo-worker1-promiser.c-pp.js:67
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — ext/wasm/fiddle/fiddle.js:255
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — ext/wasm/speedtest1-worker.js:78
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — ext/wasm/test-opfs-vfs.js:19
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — ext/wasm/tester1.c-pp.js:93
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — ext/wasm/tests/opfs/sahpool/sahpool-pausing.js:66
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Complexity conf 1.00 Very large file: ext/jni/src/org/sqlite/jni/capi/CApi.java (2899 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: ext/jni/src/org/sqlite/jni/capi/Tester1.java (2209 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: ext/jni/src/org/sqlite/jni/wrapper1/Sqlite.java (1995 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: ext/wasm/api/opfs-common-shared.c-pp.js (1306 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: ext/wasm/api/sqlite3-api-glue.c-pp.js (1964 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: ext/wasm/api/sqlite3-api-oo1.c-pp.js (2429 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: ext/wasm/api/sqlite3-api-prologue.js (2250 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: ext/wasm/api/sqlite3-vfs-kvvfs.c-pp.js (2102 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: ext/wasm/api/sqlite3-vfs-opfs-sahpool.c-pp.js (1466 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: ext/wasm/common/whwasmutil.js (2547 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: ext/wasm/tester1.c-pp.js (4593 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/history_independence_test.sh (3722 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/sql_oracle_test.sh (6978 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/vc_oracle_error_recovery_test.sh (3973 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: test/vc_oracle_feature_interaction_test.sh (13373 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/386f03f2-bb0f-4720-b17b-1325dc535281/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/386f03f2-bb0f-4720-b17b-1325dc535281/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.