sindresorhus/is-up

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.24s · analysis 3.2s · GitHub API rate-limit (preflight)

https://github.com/sindresorhus/is-up · scanned 2026-06-04 03:23 UTC (1 day, 5 hours ago) · 10 languages

15 findings (7 legacy + 8 scanner) 47th percentile · Javascript · tiny (<2K LoC) Scanner says 87 (lower by 28)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 day, 5 hours ago · v2 · 11 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`	50.0	0.15	7.50
`security_score`	100.0	0.25	25.00
`testing_score`	0.0	0.20	0.00
`documentation_score`	40.0	0.15	6.00
`practices_score`	82.0	0.15	12.30
`code_quality`	80.0	0.10	8.00
Overall		1.00	58.8

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 2 Medium 4 Low 1 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 7 9-layer 4 Crowd 0 Layer: Software 7 Quality 1 Api 1 Frontend 1 Security 1

Exclude dismissed / FP Exclude test files

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

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

high Legacy software dependency conf 0.90 ✓ Repobility Action `actions/checkout` pinned to mutable ref `@v2`

`uses: actions/checkout@v2` resolves at workflow-run time. Tags and branches can be re-pushed by the action owner; that made the tj-actions/changed-files compromise (2025) instantly affect ~23K repos. Pin to a 40-char commit SHA + lock with Dependabot or renovate.

.github/workflows/main.yml:15 dependencylegacy

high Legacy software dependency conf 0.90 ✓ Repobility Action `actions/setup-node` pinned to mutable ref `@v2`

`uses: actions/setup-node@v2` resolves at workflow-run time. Tags and branches can be re-pushed by the action owner; that made the tj-actions/changed-files compromise (2025) instantly affect ~23K repos. Pin to a 40-char commit SHA + lock with Dependabot or renovate.

.github/workflows/main.yml:16 dependencylegacy

medium Legacy software dependency conf 0.90 npm package `ava` is 5 major version(s) behind (^3.15.0 -> 8.0.1)

`ava` is pinned/resolved at ^3.15.0 but the latest stable release on the npm registry is 8.0.1 (5 major version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.

package.json dependencylegacy

medium Legacy software dependency conf 0.90 npm package `got` is 4 major version(s) behind (^11.8.2 -> 15.0.5)

`got` is pinned/resolved at ^11.8.2 but the latest stable release on the npm registry is 15.0.5 (4 major version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.

package.json dependencylegacy

medium Legacy software dependency conf 0.90 npm package `xo` is 2 major version(s) behind (^0.44.0 -> 2.0.2)

`xo` is pinned/resolved at ^0.44.0 but the latest stable release on the npm registry is 2.0.2 (2 major version(s) behind). Outdated dependencies accumulate unpatched bugs and make future security upgrades harder. This is the version-currency signal Dependabot version-update PRs raise.

package.json dependencylegacy

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: test.js

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

dead-code-candidate

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/11646c0f-12b1-42f5-94c5-c6dbac79cc89/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/11646c0f-12b1-42f5-94c5-c6dbac79cc89/

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.