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.
Sign up free Scan another repo

Schravenralph/Ruimtemeesters-Dashboarding

https://github.com/Schravenralph/Ruimtemeesters-Dashboarding · scanned 2026-06-16 00:04 UTC (2 months, 3 weeks ago)

405 raw signals (213 security + 192 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
66.9
/100
Security checks
67
9 findings
System graph
67
100.0% cov · 185 findings
Critical
2
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 12 Medium 16 Low 83 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 185 Crowd 0 Layer: Quality 89 Security 1 Frontend 43 Hardware 2 Cicd 1 Api 58

Last 1 scan of this repo. Each new scan persists a full payload — historical comparison is exact, not lossy.

v1
Jun 16 00:04
v#IDStatusScoreGapsNodesCommitStarted
v scan_65e0ccfe9ed7 ok 66.9 192 2587 1b7f82b Jun 16 00:04
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/51750bb8-9dce-409e-98a5-a9cf3e2e38d7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/51750bb8-9dce-409e-98a5-a9cf3e2e38d7/

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.