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.

wrzonance/SpecR

https://github.com/wrzonance/SpecR · scanned 2026-06-16 01:00 UTC (2 months, 1 week ago)

81 raw signals (0 security + 81 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 81 findings

Severity distribution — click a segment to filter

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

Severity: Critical 0 High 0 Medium 20 Low 38 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 81 Crowd 0 Layer: Frontend 4 Hardware 1 Security 1 Cicd 4 Quality 38 Api 33

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 71.0/100 with 100.0% coverage. It contains 1191 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 81 findings — concentrated in quality (38), api (33), frontend (4). Risk profile is low: 0 critical, 0 high, 20 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 2 of 81 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/gen-text-fixtures.ts:19

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 — scripts/load-files.ts:29

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/ad6f9086-a1cc-4c76-94c7-16fc059dd11e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ad6f9086-a1cc-4c76-94c7-16fc059dd11e/

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.