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.

shakacode/react_on_rails

https://github.com/shakacode/react_on_rails · scanned 2026-06-16 00:09 UTC (2 months, 2 weeks ago)

363 raw signals (0 security + 363 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
11 healthy 6 warning
GET /health
warning
endpoint 1 gap risk 0.45
GET /info
warning
endpoint 2 gaps risk 0.45
A page
healthy
page risk 0.40
B page
healthy
page risk 0.40
Client Component page
healthy
page risk 0.40
First Page page
healthy
page risk 0.40
React Router page
healthy
page risk 0.40
Second Page page
healthy
page risk 0.40
Simple Server page
healthy
page risk 0.40
GET /ready
warning
endpoint 1 gap risk 0.05
auth
POST /contacts
warning
endpoint 1 gap risk 0.05
auth
POST /probe/stream
warning
endpoint 2 gaps risk 0.05
auth
POST /probe/unary
warning
endpoint 2 gaps risk 0.05
auth
A page
healthy
page
auth
B page
healthy
page
auth
Home page
healthy
page
auth
Products page
healthy
page
auth
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/ba5c8749-6593-4668-8546-ac87a95f88c6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ba5c8749-6593-4668-8546-ac87a95f88c6/

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.