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.

allmonday/pydantic-resolve

https://github.com/allmonday/pydantic-resolve · scanned 2026-05-14 22:54 UTC (3 weeks ago) · 10 languages

95 findings (14 legacy + 81 scanner) 92nd percentile · Python · medium (20-100K LoC) Scanner says 78 (higher by 6)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 3 weeks ago · v1 · 14 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Score breakdown â 2026-05-17-v4 calibration-aware
Component Sub-score Weight Contribution
structure_score 75.0 0.15 11.25
security_score 94.2 0.25 23.55
testing_score 100.0 0.20 20.00
documentation_score 86.0 0.15 12.90
practices_score 65.0 0.15 9.75
code_quality 67.5 0.10 6.75
Overall 1.00 84.2
Calibrated penalty buckets (security_score): web: 1.6 · agent: 2.2 · authz: 2.1
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

Top 0 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

No actionable gaps — clean repo.

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/6d3ddcb7-eec1-4398-b7e5-db12d3f2e492/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6d3ddcb7-eec1-4398-b7e5-db12d3f2e492/

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.