@markjaquith/agency@3.15.0
Manage agentic work across repositories with durable workbases
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe postinstall automatically installs a first-party Pi extension, which warrants a warning under the agent extension lifecycle policy. The ownership checks and explicit workbase integration sync do not establish malicious behavior.
Decision evidence
public snapshot- The postinstall hook installs a package-owned Pi extension into the user's global Pi extension directory.
- The installer only updates an existing extension when its ownership record and content hash match; otherwise it skips the file.
- The workbase integration target is project-local, and its sync command is an explicit CLI operation.
- The flagged process and review files use process spawning for application operations; the inspected excerpts show no malicious command or network behavior.
- The flagged Babel file is ordinary dependency code.
- The global Pi extension installation happens automatically during npm postinstall, without a consent prompt in the inspected installer path.
Source & flagged code
8 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.
src/utils/interactive-loader.tsView on unpkg · L3Findings
Affected versions and remediation
This report applies to @markjaquith/agency@3.15.0.
See all versions of @markjaquith/agency for other recorded verdicts.
- Review the evidence and your use of @markjaquith/agency@3.15.0 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.