@aui.io/apollo@0.1.76
Apollo operator console — CLI + interactive TUI
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe inspected flagged files contain ordinary dependency and Apollo product code. The automatic shell integration is package-aligned and identifiable; the source inspected did not establish a malicious attack surface.
Decision evidence
public snapshot- The package entrypoint and postinstall hook match an operator console with CLI and terminal UI components; the shell setup appends an Apollo shell integration line.
- The flagged YAML file describes ordinary input tokenization.
- The flagged Commander file imports Node child_process as part of a CLI library; other flagged files contain Apollo IDE, authentication, management, diagnostic, and Claude adapter code.
- The flagged OpenTUI bundle excerpt contains standard JavaScript export helper code.
- The postinstall hook modifies existing shell startup files, but the setup script appends an Apollo-specific shell integration line and skips CI or an explicit opt-out.
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.76.
See all versions of @aui.io/apollo for other recorded verdicts.
- Review the evidence and your use of @aui.io/apollo@0.1.76 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.