AI Security Review
scanned 3d ago · by lpm-firewall-aiLPM blocks this version under the AI-agent control-surface policy. The package mutates Pi agent control-surface state from an npm lifecycle path. During postinstall it runs setup and may schedule a worker that edits Pi settings and removes legacy pire-browser registrations/shims.
Decision evidence
public snapshot- package.json defines postinstall: node scripts/pi-postinstall.mjs.
- scripts/pi-postinstall.mjs runs bin/pire-browser.js setup during install.
- scripts/pi-postinstall.mjs schedules scripts/pi-install-migration.mjs after install when Pi-managed.
- scripts/pi-install-migration.mjs can rewrite settings.json, unlink legacy extension shim, and rename legacy managed install dirs.
- bin/pire-browser.js pi repair writes repair reports under user data and can mutate Pi settings on command.
- Behavior is mostly package-aligned for a Firefox/Pi browser automation bridge.
- No credential harvesting or arbitrary env/file exfiltration found in inspected JS/TS sources.
- Network update check uses npm CLI at runtime and is disabled during postinstall setup.
- child_process use launches native optional dependency, npm/pi update commands, or package helper scripts.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage contains a possible secret pattern.
extension/dist/background.jsView on unpkg · L21This package version adds a dangerous source file absent from the previous stored version.
bin/pire-browser.jsView on unpkgPackage source references child process execution.
bin/pire-browser.jsView on unpkg · L1Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
scripts/pi-postinstall.mjsView on unpkg · L2