agency-lang@0.30.0
⚠ Under reviewThe Agency language
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe inspected agent setup is explicit CLI functionality, and the manifest shows no install lifecycle hook. The required clean citation coverage exceeds the available citation limit, so the decision remains unresolved.
Decision evidence
public snapshot- package.json exposes a CLI entrypoint and its scripts contain no install lifecycle hook.
- Agent configuration writes are reached through explicit `agency lsp setup` and `agency mcp setup codex` commands.
- The LSP helper writes project configuration, and the MCP helper updates a specified config file.
- The manifest and inspected setup paths do not establish automatic installation-time agent configuration changes or credential transfer.
- The clean verdict requires citations for more source paths than the output limit permits.
Source & flagged code
6 flaggedPackage source references dynamic require/import behavior.
dist/lib/optimize/optimizerModule.jsView on unpkg · L32Source writes installer persistence such as shell profile or service configuration.
dist/lib/cli/schedule/backends/launchd.jsFindings
Affected versions and remediation
This report applies to agency-lang@0.30.0.
See all versions of agency-lang for other recorded verdicts.
- Review the evidence and your use of agency-lang@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.