@agimon-ai/po-container-runtime-linux-arm64@0.0.1-alpha.26
Read-only Po server payload for Linux arm64 sandbox containers, mounted at /opt/po and run with Node 24.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest describes a read-only Linux arm64 server payload, with no install lifecycle hook and only metadata exports. The inspected launcher and startup initialization are consistent with running the bundled Po server; the scanner’s credential pointers were leads and did not establish an attack chain.
Decision evidence
public snapshot- The manifest describes a read-only Linux arm64 Po server payload and exposes only its runtime metadata.
- The build script builds the runtime bundle and copies its runtime configuration; no install, preinstall, or postinstall hook is declared.
- The runtime config points to the Po server entry, and its launcher supervises that server when started.
- Startup initializes the Po agent directory and attempts a Po home migration; this is consistent with the runtime’s stated purpose.
Source & flagged code
6 flaggedThe scanner resource watchdog stopped semantic analysis before full coverage; route this package to AI without publishing a static verdict.
The manifest describes a read-only Linux arm64 Po server payload and exposes only its runtime metadata.
package.jsonView on unpkg · L3The build script builds the runtime bundle and copies its runtime configuration; no install, preinstall, or postinstall hook is declared.
package.jsonFindings
Affected versions and remediation
This report applies to @agimon-ai/po-container-runtime-linux-arm64@0.0.1-alpha.26.
See all versions of @agimon-ai/po-container-runtime-linux-arm64 for other recorded verdicts.
- Review the evidence and your use of @agimon-ai/po-container-runtime-linux-arm64@0.0.1-alpha.26 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.