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

Scan timing: clone 1.37s · analysis 19.47s · 1.8 MB · GitHub API rate-limit (preflight)

d3/d3

https://github.com/d3/d3 · scanned 2026-06-05 05:32 UTC (4 hours, 29 minutes ago) · 10 languages

71 findings (49 legacy + 22 scanner) 41st percentile · Javascript · small (2-20K LoC) Scanner says 92 (lower by 18)

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

Complete repo analysis

Last scanned 4 hours, 29 minutes ago · v2 · 60 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
84.3
/100
Repobility
76
49 legacy
9-layer
92
55.6% cov · 11 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 100.0 0.15 15.00
security_score 55.0 0.25 13.75
testing_score 75.0 0.20 15.00
documentation_score 60.0 0.15 9.00
practices_score 90.0 0.15 13.50
code_quality 80.0 0.10 8.00
Overall 1.00 74.2
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 20 Medium 23 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 49 9-layer 11 Crowd 0 Layer: Software 52 Api 1 Frontend 4 Security 1 Cicd 2

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 2 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.
2 matching findings on this repo
  • high Action `actions/configure-pages` pinned to mutable ref `@v4` .github/workflows/deploy.yml:30
  • low File has no detected symbols: rollup.config.js
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/dce91b8d-f985-40da-acf1-293c651e1fb2/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/dce91b8d-f985-40da-acf1-293c651e1fb2/

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.