@aui.io/apollo@0.1.71
Apollo operator console — CLI + interactive TUI
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe flagged source paths show ordinary parser, CLI, IDE launch, authentication, API, and diagnostic behavior. The postinstall shell setup is a package-aligned convenience with CI and opt-out guards; no concrete malicious behavior was found.
Decision evidence
public snapshot- package.json runs an OpenTUI dependency repair and shell integration setup during postinstall.
- The repair script installs only the declared OpenTUI dependencies when their package files are missing.
- The shell setup appends a guarded Apollo shell integration line to zsh/bash startup files and skips CI or an explicit opt-out.
- The inspected flagged runtime files contain YAML parsing, CLI command handling, local IDE launching, browser login, API requests, bundled runtime code, and doctor diagnostics.
- Postinstall can modify shell startup files in the user home directory without a separate setup command.
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.71.
See all versions of @aui.io/apollo for other recorded verdicts.
- Review the evidence and your use of @aui.io/apollo@0.1.71 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.