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.
Sign up free Scan another repo
48 of your 156 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 64.96s for a 138.0 MB repo slow.
  • Repobility's analysis ran in 25.19s after the clone landed.

nocodb/nocodb

https://github.com/nocodb/nocodb · scanned 2026-06-05 09:04 UTC (5 days, 19 hours ago) · 10 languages

1640 raw signals (130 security + 1510 graph) 10/13 scanners ran 5th percentile · Typescript · huge (>500K LoC) System graph score 55 (higher by 15)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
65.8
/100
Security checks
77
67 findings
System graph
55
100.0% cov · 733 findings
Critical
13
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 37.0 0.20 7.40
documentation_score 64.0 0.15 9.60
practices_score 74.0 0.15 11.10
code_quality 80.0 0.10 8.00
Overall 1.00 70.1
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
Severity: Critical 13 High 36 Medium 17 Low 312 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 67 System graph 733 Crowd 0 Layer: Quality 242 Security 31 Cicd 17 Software 59 Frontend 386 Hardware 1 Api 64

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in packages/nocodb/src/types/nc-plugin/common/XcUIBuilder.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in packages/nocodb/src/types/nc-plugin/common/XcUIBuilder.ts:46; move to env var / secrets manager.
packages/nocodb/src/types/nc-plugin/common/XcUIBuilder.ts:46
#2
Possible secret in packages/nocodb/src/modules/auth/ui/auth/resetPassword.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in packages/nocodb/src/modules/auth/ui/auth/resetPassword.ts:89; move to env var / secrets manager.
packages/nocodb/src/modules/auth/ui/auth/resetPassword.ts:89
#3
Possible secret in packages/nocodb/src/services/base-users/ui/auth/resetPassword.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in packages/nocodb/src/services/base-users/ui/auth/resetPassword.ts:89; move to env var / secrets manager.
packages/nocodb/src/services/base-users/ui/auth/resetPassword.ts:89
#4
Possible secret in packages/nocodb/src/run/testDocker.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in packages/nocodb/src/run/testDocker.ts:49; move to env var / secrets manager.
packages/nocodb/src/run/testDocker.ts:49
#5
Possible secret in packages/nocodb/src/run/testDocker.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in packages/nocodb/src/run/testDocker.ts:60; move to env var / secrets manager.
packages/nocodb/src/run/testDocker.ts:60
#6
Possible secret in packages/nocodb/src/run/testDocker.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in packages/nocodb/src/run/testDocker.ts:73; move to env var / secrets manager.
packages/nocodb/src/run/testDocker.ts:73
#7
Possible secret in packages/nc-secret-mgr/src/nocodb/cli.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in packages/nc-secret-mgr/src/nocodb/cli.js:2; move to env var / secrets manager.
packages/nc-secret-mgr/src/nocodb/cli.js:2
#8
Possible secret in packages/nc-secret-mgr/src/nocodb/cli.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in packages/nc-secret-mgr/src/nocodb/cli.js:2; move to env var / secrets manager.
packages/nc-secret-mgr/src/nocodb/cli.js:2
#9
Possible secret in packages/nc-secret-mgr/src/nocodb/cli.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in packages/nc-secret-mgr/src/nocodb/cli.js:2; move to env var / secrets manager.
packages/nc-secret-mgr/src/nocodb/cli.js:2
#10
Possible secret in packages/nc-gui/utils/baseCreateUtils.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in packages/nc-gui/utils/baseCreateUtils.ts:119; move to env var / secrets manager.
packages/nc-gui/utils/baseCreateUtils.ts:119

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/ac9bfbed-85b8-40b6-bc96-88903626f9c2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ac9bfbed-85b8-40b6-bc96-88903626f9c2/

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.