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.

Sumyabazar00/neon-wave

https://github.com/Sumyabazar00/neon-wave · scanned 2026-06-16 00:25 UTC (2 months, 2 weeks ago)

8 raw signals (0 security + 8 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

44.4% cov · 8 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

Exclude dismissed / FP Exclude test files

No flows synthesized yet.

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/2e28be20-225e-4e6e-bb14-a68ab2697250/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2e28be20-225e-4e6e-bb14-a68ab2697250/

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.