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.

langflow-ai/openrag

https://github.com/langflow-ai/openrag · scanned 2026-05-15 19:40 UTC (2 weeks, 6 days ago) · 10 languages

456 findings (97 legacy + 359 scanner) 17th percentile · Python · large (100-500K LoC) Scanner says 65 (lower by 4)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 6 days ago · v1 · 82 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 85.0 0.15 12.75
security_score 16.1 0.25 4.03
testing_score 71.0 0.20 14.20
documentation_score 88.0 0.15 13.20
practices_score 75.0 0.15 11.25
code_quality 57.9 0.10 5.79
Overall 1.00 61.2
Calibrated penalty buckets (security_score): web: 1.6 · agent: 2.1 · authz: 11.4 · docker: 46.5 · threat: 18.9 · journey: 44.4
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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

v1
May 15 19:39
v#IDStatusScoreGapsNodesCommitStarted
v scan_a05af60d33cc ok 65.4 359 4017 afe80ab May 15 19:39
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/2450297c-75ff-442e-9242-a0e495d24189/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2450297c-75ff-442e-9242-a0e495d24189/

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.