withastro/astro

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.

https://github.com/withastro/astro · scanned 2026-05-16 12:50 UTC (3 weeks, 3 days ago) · 10 languages

537 raw signals (20 security + 517 graph) 2/10 scanners ran 33rd percentile · Typescript · large (100-500K LoC) System graph score 64 (higher by 6)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 3 weeks, 5 days ago · v1 · 5 actionable findings from 1 signal source. 4 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 0 findings

Score breakdown â 2026-05-17-v4 calibration-aware

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	94.0	0.25	23.50
`testing_score`	62.0	0.20	12.40
`documentation_score`	60.0	0.15	9.00
`practices_score`	55.0	0.15	8.25
`code_quality`	80.0	0.10	8.00
Overall		1.00	70.2

Calibrated penalty buckets (security_score): threat: 6.0

security_score may be inflated — optional scanners skipped due to repo size/fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 2 Low 1 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 5 System graph 0 Crowd 0 Layer: Quality 2 Security 1 Software 2

Exclude dismissed / FP Exclude test files

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 1 finding

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.

1 matching finding on this repo

high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… packages/astro/src/transitions/router.ts:443

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/3180692a-45fb-463e-ba11-8c05f120b094/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3180692a-45fb-463e-ba11-8c05f120b094/

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.