junit-team/junit5

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.

https://github.com/junit-team/junit5.git · scanned 2026-05-16 11:56 UTC (3 weeks, 3 days ago) · 10 languages

89 raw signals (14 security + 75 graph) 64th percentile · Java · large (100-500K LoC) System graph score 96 (lower by 20)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 3 weeks, 3 days ago · v3 · 3 actionable findings from 1 signal source. 9 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

66.7% cov · 0 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 0 Low 1 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 3 System graph 0 Crowd 0 Layer: Quality 1 Software 2

Exclude dismissed / FP Exclude test files

No flows synthesized yet.

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/45a36d70-01b0-4b5b-9ba6-85f148bda10b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/45a36d70-01b0-4b5b-9ba6-85f148bda10b/

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.