@herjarsa/omo-meta-governor@0.31.4
Self-judging agent orchestration layer for OpenCode. Reads memory, scores sessions, dispatches decisions.
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The flagged child-process and installation capabilities are conditional or package-aligned in the inspected code, so the scanner hints do not support a malicious verdict.
Decision evidence
public snapshot- package.json has no install lifecycle hook; its scripts are build, typecheck, and test.
- The required agent-integration locations in dist/index.js and dist/lib.js check plan-file content and completion markers.
- The lib.js package installation path is conditional on the autoInstall option.
- The runtime npm view check compares the registry version and emits a warning when the cache is stale.
- The MCP server excerpt formats code-analysis caller information; it does not show an attack.
- dist/lib.js contains child-process and package-install capabilities, but the inspected install path is option-gated and no concrete attack behavior was established.
Source & flagged code
7 flagged · loading sourcePackage source invokes a package manager install command at runtime.
dist/lib.jsFindings
Affected versions and remediation
This report applies to @herjarsa/omo-meta-governor@0.31.4.
See all versions of @herjarsa/omo-meta-governor for other recorded verdicts.
- Review the evidence and your use of @herjarsa/omo-meta-governor@0.31.4 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.