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.

Yuting02/spark-island

https://github.com/Yuting02/spark-island · scanned 2026-06-16 01:09 UTC (2 months, 1 week ago)

52 raw signals (0 security + 52 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 52 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 52 findings

Severity distribution — click a segment to filter

Active filters: layer: frontend × excluding tests × Reset all

Severity: Critical 0 High 0 Medium 13 Low 37 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 52 Crowd 0 Layer: Frontend 3 Security 10 Cicd 1 Quality 6 Api 32

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 83.2/100 with 88.9% coverage. It contains 207 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 52 findings — concentrated in api (32), security (10), quality (6). Risk profile is low: 0 critical, 0 high, 13 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/seed.js:14

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

Fq console leak

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — server/index.js:30

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

Fq 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/ff90ae5b-6011-4c6c-abd6-25120d5a7a49/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ff90ae5b-6011-4c6c-abd6-25120d5a7a49/

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.