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

ruozhuoruoyu/Philont-Agent

https://github.com/ruozhuoruoyu/Philont-Agent · scanned 2026-06-15 23:57 UTC (2 months, 3 weeks ago)

154 raw signals (0 security + 154 graph)

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

Complete repo analysis

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

JSON
Combined
58.1
/100
Security checks
58
0 findings
System graph
58
100.0% cov · 154 findings
Critical
1
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 1 High 2 Medium 30 Low 74 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 154 Crowd 0 Layer: Api 1 Frontend 60 Hardware 3 Security 16 Cicd 1 Quality 73

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

v1
Jun 15 23:57
v#IDStatusScoreGapsNodesCommitStarted
v scan_c3e0935d2009 ok 58.1 154 2200 a200f08 Jun 15 23:57
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/72101aa7-0686-452a-82ab-e8d17691dc5d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/72101aa7-0686-452a-82ab-e8d17691dc5d/

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.