@aui.io/apollo@0.1.69
Apollo operator console — CLI + interactive TUI
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe automatic shell startup edit is a real persistent install-time behavior, so a warning is appropriate. The inspected code connects it to Apollo's stated workspace integration and provides opt-out and removal paths; the scanner similarity labels alone do not establish malicious behavior.
Decision evidence
public snapshot- The postinstall hook runs shell setup automatically.
- The shell setup appends an Apollo command to existing shell startup files, unless CI or an opt-out variable is set.
- That command evaluates output from `apollo shell-init` when a shell starts; the code labels it as workspace auto-cd integration and provides a removal marker.
- A separate postinstall repair path only reinstalls declared OpenTUI dependencies when package files are missing.
- The shell startup change is visibly tied to Apollo workspace integration and is marked for removal; the code supports an opt-out.
- The OpenTUI repair checks for missing package files before reinstalling declared dependencies.
- The CLI entrypoint delegates to the bundled Apollo CLI.
Source & flagged code
12 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.69.
See all versions of @aui.io/apollo for other recorded verdicts.
- Review the evidence and your use of @aui.io/apollo@0.1.69 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.