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

Scan timing: clone 7.13s · analysis 4.23s · 10.5 MB · GitHub API rate-limit (preflight)

Baskerville42/outage-data-ua

https://github.com/Baskerville42/outage-data-ua · scanned 2026-06-06 00:58 UTC (4 days, 1 hour ago) · 10 languages

73 raw signals (31 security + 42 graph) 66th percentile · Javascript · tiny (<2K LoC) System graph score 87 (lower by 16)

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

Complete repo analysis

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

JSON
Combined
80.0
/100
Security checks
73
16 findings
System graph
87
66.7% cov · 7 findings
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 65.0 0.15 9.75
security_score 82.5 0.25 20.62
testing_score 70.0 0.20 14.00
documentation_score 73.7 0.15 11.05
practices_score 74.0 0.15 11.10
code_quality 50.0 0.10 5.00
Overall 1.00 71.5
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 3 Medium 8 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 16 System graph 7 Crowd 0 Layer: Quality 11 Software 6 Cicd 2 Api 1 Frontend 2 Security 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.

Commented-out code 1 finding
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
1 matching finding on this repo
  • info Commented-code block (7 lines) in templates/html/schedule-shared.js:888
View all commented-out code 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/168353bb-b770-4fb6-b546-61194933e485/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/168353bb-b770-4fb6-b546-61194933e485/

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.