@herjarsa/omo-meta-governor@0.30.0
Self-judging agent orchestration layer for OpenCode. Reads memory, scores sessions, dispatches decisions.
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe package has no npm install lifecycle hook, so blocking is not supported. Its normal plugin activation nevertheless defaults to global external tooling setup and synthetic agent directives, creating a concrete non-blocking agent-extension risk.
Decision evidence
public snapshot- The package exports both bundled JavaScript entrypoints.
- The main bundle invokes its CLI setup during plugin initialization with automatic installation, upgrades, and global scope as defaults.
- The secondary bundle contains the same automatic CLI setup path.
- The setup tries multiple Python package installation commands for cli-anything-hub.
- The plugin injects a synthetic user message directing commits to local, fork, and upstream repositories.
- package.json has no preinstall, install, or postinstall lifecycle script.
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.30.0.
See all versions of @herjarsa/omo-meta-governor for other recorded verdicts.
- Review the evidence and your use of @herjarsa/omo-meta-governor@0.30.0 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.