Standalone Go daemon bridging Homematic / HomeMatic IP CCUs to MQTT (with Home Assistant Discovery), a REST + WebSocket API, an MCP server, a Svelte config UI, and a native Matter bridge — multi-CCU, single static binary.
- capability exposure inferred + 10
- recent drift inferred + 20
- tool safety inferred + 12
- trust mitigators mixed − 3
inferred mixed
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.
graded 9m ago · see ecosystem CVEs →
- B · 31 → C · 39
- A · 0 → B · 31
No known CVEs for this server.
- high dangerous code
committed secret: private key
analyzed commit c880f5f · analyzer v28 · 1d ago
skills & prompt files 1
- agent-rules SukramJ-openccu-loom-c880f5f/CLAUDE.md
danger signals1
- committed secret private key SukramJ-openccu-loom-c880f5f/internal/north/matter/secure/attestation/testpaa.go :121
PEM private key block (redacted)
- recent drift +20 capability drift →
[](https://mcpobservatory.com/servers/github:SukramJ/openccu-loom/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 SukramJ.