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

VectifyAI/OpenKB

https://github.com/VectifyAI/OpenKB · scanned 2026-05-15 03:47 UTC (3 weeks ago) · 10 languages

13 findings (1 legacy + 12 scanner) 85th percentile · Python · small (2-20K LoC) Scanner says 96 (lower by 12)

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

Complete repo analysis

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

JSON
Combined
90.9
/100
Repobility
86
1 legacy
9-layer
96
66.7% cov · 0 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-14-v3
Component Sub-score Weight Contribution
structure_score 75.0 0.15 11.25
security_score 100.0 0.25 25.00
testing_score 100.0 0.20 20.00
documentation_score 73.0 0.15 10.95
practices_score 65.0 0.15 9.75
code_quality 68.3 0.10 6.83
Overall 1.00 83.8
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 1 Medium 0 Low 0 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 1 9-layer 0 Crowd 0 Layer: Quality 1
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/e14443d6-d133-4e8f-b399-5f52bf6a750f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e14443d6-d133-4e8f-b399-5f52bf6a750f/

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.