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

Scan timing: clone 1.21s · analysis 0.18s · GitHub API rate-limit (preflight)

sindresorhus/is-online

https://github.com/sindresorhus/is-online.git · scanned 2026-05-19 12:46 UTC (2 weeks, 3 days ago) · 10 languages

25 findings (5 legacy + 20 scanner) 53rd percentile · Javascript · tiny (<2K LoC) Scanner says 90 (lower by 27)

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

Complete repo analysis

Last scanned 2 weeks, 3 days ago · v2 · 15 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
82.3
/100
Repobility
74
5 legacy
9-layer
90
66.7% cov · 10 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 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 0.0 0.20 0.00
documentation_score 60.0 0.15 9.00
practices_score 82.0 0.15 12.30
code_quality 80.0 0.10 8.00
Overall 1.00 63.3
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 0 Medium 2 Low 6 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 5 9-layer 10 Crowd 0 Layer: Quality 4 Software 5 Api 1 Frontend 4 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.

Fragile runtime 3 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
3 matching findings on this repo
  • info [MINED043] Http Not Https: Hardcoded http:// (not localhost) for endpoints that… test.js:64
  • info [MINED044] Js Console Log Prod: console.log left in code. Should be replaced wi… browser-test.manual.js:7
  • medium `fetch()` without try/.catch or AbortSignal — browser.js:26
View all fragile runtime 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/6a5d08b2-2318-41e3-bbb7-58c2ec7053ea/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/6a5d08b2-2318-41e3-bbb7-58c2ec7053ea/

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.