AI Security Review
scanned 11d ago · by lpm-firewall-aiNo confirmed malicious attack surface in the inspected npm source. The install hook is a package-aligned binary installer for the Apteva CLI, with broad agent capabilities only after user invocation.
Decision evidence
public snapshot- package.json runs postinstall: node install.js
- install.js downloads a platform tarball from GitHub releases and extracts it with tar
- install.js writes binaries, tarballs, and symlinks under APTEVA_HOME default ~/.apteva
- cli.js spawns the resolved apteva binary and passes through process.env
- No code writes Claude/Codex/Cursor/MCP config or other foreign AI-agent control surfaces
- No credential harvesting or outbound exfiltration logic found in JS source
- Network access is package-aligned to github.com/apteva/apteva release assets
- Install-time writes are limited to package install dir and first-party ~/.apteva namespace
- Runtime agent capabilities are activated by user invoking the apteva CLI
Source & flagged code
4 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 unpkgA single source file combines environment access, network access, and code or shell execution; review context before blocking.
install.jsView on unpkg · L27