sindresorhus/is-online

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.

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)

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

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

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

Exclude dismissed / FP Exclude test files

Scan summary Repository scanned at 90.2/100 with 66.7% coverage. It contains 30 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 10 findings — concentrated in frontend (4), software (3), api (1). Risk profile is low: 0 critical, 0 high, 2 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 7 of 15 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium 9-layer quality integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — browser.js:26

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

integrityfragile-runtimerobustness

medium 9-layer security coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). Either auth lives in custom code, in a separate service, or is missing.

coverageauth

low 9-layer software dead-code-candidate conf 1.00 File has no detected symbols: browser-test.manual.js

Source file with no class/function declarations — possible config, dead code, or scratch file.

dead-code-candidate

low 9-layer software dead-code-candidate conf 1.00 File has no detected symbols: index.test-d.ts

Source file with no class/function declarations — possible config, dead code, or scratch file.

dead-code-candidate

low 9-layer software dead-code-candidate conf 1.00 File has no detected symbols: test.js

Source file with no class/function declarations — possible config, dead code, or scratch file.

dead-code-candidate

low 9-layer frontend frontend-quality conf 1.00 Stray `console.log` in TS/JS — browser-test.manual.js:7

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

frontend-qualityfq.console-leak

low 9-layer frontend frontend-quality conf 1.00 Stray `console.log` in TS/JS — index.d.ts:25

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

frontend-qualityfq.console-leak

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.