@aui.io/apollo@0.1.90
Apollo CLI — author, test and operate Apollo-1 agents from your terminal (scriptable CLI + interactive TUI)
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe postinstall’s shell-file change is an explicit Apollo CLI convenience, and the inspected entrypoint and flagged source excerpts show no concrete malicious behavior. The scanner hints alone do not establish an attack.
Decision evidence
public snapshot- package.json wires the postinstall to OpenTUI repair and Apollo shell setup, and pins the related Apollo packages to the same release.
- Shell setup appends a guarded Apollo shell-init line, skips CI and an opt-out flag, and avoids duplicate insertion.
- The Apollo shell hook supports auto-changing directories after Apollo workspace commands; this is local CLI integration.
- The inspected doctor excerpt runs a command with a two-second timeout; the IDE launcher excerpt detects local editor launchers.
- The inspected bundled excerpts show module exports, standard Commander imports, and a limited Claude Code file-tool list.
Source & flagged code
10 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references dynamic require/import behavior.
bin/apollo.jsView on unpkg · L10Findings
Affected versions and remediation
This report applies to @aui.io/apollo@0.1.90.
See all versions of @aui.io/apollo for other recorded verdicts.
- Review the evidence and your use of @aui.io/apollo@0.1.90 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.