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.

adamklie/greenroom

https://github.com/adamklie/greenroom · scanned 2026-06-17 01:29 UTC (1 month, 2 weeks ago)

114 raw signals (0 security + 114 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -29.0 (diff) · 104 actionable findings from 1 signal source. 10 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 · 104 findings

Severity distribution — click a segment to filter

Active filters: search: "duplicates" × excluding tests × Reset all

Severity: Critical 0 High 7 Medium 14 Low 71 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 104 Crowd 0 Layer: Software 7 Frontend 8 Hardware 4 Security 2 Cicd 1 Quality 26 Api 56

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 47.7/100 with 100.0% coverage. It contains 976 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 114 findings — concentrated in api (56), quality (31), software (9). Risk profile is high: 0 critical, 7 high, 14 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 1 of 104 actionable findings. 114 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

low System graph api Wiring conf 1.00 Unused endpoint: GET /duplicates

`backend/app/routers/dedup.py` declares `GET /duplicates` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

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/0df45938-f509-45df-8761-150733f11b3d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0df45938-f509-45df-8761-150733f11b3d/

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.