Authorization-first, deterministic BOLA/IDOR validation for HTTP APIs
- capability exposure inferred + 32
- recent drift inferred + 20
- tool safety inferred + 12
inferred
The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.
grade last moved 3d ago · see ecosystem CVEs →
- C · 46 → D · 64
- C · 38 → C · 46
No known CVEs for this server.
- high dangerous code
committed secret: Stripe live key · dynamic exec: unsafe yaml.load()
analyzed commit fde23cf · analyzer v33 · 1w ago
skills & prompt files 1
- agent-rules LeonardSEO-OpenBOLA-fde23cf/AGENTS.md
danger signals2
- dynamic code execution unsafe yaml.load() LeonardSEO-OpenBOLA-fde23cf/src/openbola/scope.py :328
raw_document = yaml.load( - committed secret Stripe live key LeonardSEO-OpenBOLA-fde23cf/tests/test_state.py :586
sk_liv…(28 chars, redacted)
- recent drift +20 capability drift →
[](https://mcpobservatory.com/servers/github:LeonardSEO/OpenBOLA/security) Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of LeonardSEO.