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

Zen-TM/logjam

https://github.com/Zen-TM/logjam · scanned 2026-06-16 01:11 UTC (2 months, 1 week ago)

159 raw signals (15 security + 144 graph)

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

Complete repo analysis

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

JSON
Combined
60.0
/100
Security checks
60
8 findings
System graph
60
100.0% cov · 131 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 3 Medium 23 Low 68 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 131 Crowd 0 Layer: Quality 75 Software 2 Frontend 2 Hardware 5 Security 2 Cicd 3 Api 50

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

v1
Jun 16 01:11
v#IDStatusScoreGapsNodesCommitStarted
v scan_78d3cc3bd6df ok 60.0 144 1760 13d58d4 Jun 16 01:11
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/0985ac3d-7eaf-4579-a62c-cd41d798114e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0985ac3d-7eaf-4579-a62c-cd41d798114e/

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.