registry / petbox-wire / 0.1.0-ci.767

petbox-wire@0.1.0-ci.767

Wire any project to PetBox (Claude Code, opencode, Factory Droid) — global hooks, MCP configs and skills — with a single npx command, no repo clone.

AI Security Review

scanned 12d ago · by lpm-firewall-ai

LPM treats this as warn-only first-party agent extension lifecycle risk. The package is a CLI that explicitly wires projects into PetBox by installing first-party agent hooks, MCP configs, skills, and an opencode plugin. This is a real agent extension lifecycle risk but not unconsented install-time hijack.

Static reason

No blocking static signals were detected.; previous stored version diff introduced dangerous source

Trigger

User runs npx petbox-wire <dir> <project> --key <KEY>

Impact

Configured agents may send session transcripts and memory lookups to PetBox for registered projects; API keys are persisted locally.

Mechanism

explicit agent hook/plugin and MCP configuration setup

Rationale

Source inspection shows an explicit agent-wiring CLI with broad local config writes and transcript network sync, but no npm lifecycle trigger, stealth persistence, credential exfiltration beyond the configured PetBox service, or remote payload execution. Under the agent control-surface policy this should warn for first-party extension lifecycle risk rather than block.

Evidence

package.jsonbin/petbox-wire.jssrc/wire.tssrc/posix-env.tssrc/registry.tssrc/append.tssrc/push-session.tssrc/pull-memory.tssrc/canon.tsREADME.md~/.petbox/wire/~/.petbox/keys.json~/.petbox/env.sh~/.petbox/projects.json~/.claude/settings.json

petbox-wire@0.1.0-ci.767

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code