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
67 of your 129 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 3.25s · analysis 12.89s · 15.3 MB · GitHub API rate-limit (preflight)

drasi-project/drasi-core

https://github.com/drasi-project/drasi-core · scanned 2026-06-05 22:09 UTC (1 week, 2 days ago) · 10 languages

245 raw signals (121 security + 124 graph) 49th percentile · Rust · large (100-500K LoC) System graph score 78 (lower by 12)

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

Complete repo analysis

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

JSON
Combined
73.9
/100
Security checks
69
35 findings
System graph
79
100.0% cov · 43 findings
Critical
9
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 56.0 0.25 14.00
testing_score 63.0 0.20 12.60
documentation_score 70.0 0.15 10.50
practices_score 82.0 0.15 12.30
code_quality 48.3 0.10 4.83
Overall 1.00 67.0
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 9 High 10 Medium 10 Low 31 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 35 System graph 43 Crowd 0 Layer: Cicd 15 Quality 42 Software 5 Security 13 Network 1 Hardware 1 Frontend 1

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Config drift 4 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
4 matching findings on this repo
  • critical Possible secret in components/mssql-common/src/config.rs components/mssql-common/src/config.rs:252
  • critical Possible secret in components/reactions/storedproc-postgres/src/config.rs components/reactions/storedproc-postgres/src/conf…:51
  • critical Possible secret in components/reactions/storedproc-mysql/src/config.rs components/reactions/storedproc-mysql/src/config.…:50
  • critical Possible secret in components/reactions/storedproc-mssql/src/config.rs components/reactions/storedproc-mssql/src/config.…:50
View all config drift findings →
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/53f24a18-76d5-4efb-9204-e2b73b09ea39/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/53f24a18-76d5-4efb-9204-e2b73b09ea39/

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.