@markjaquith/agency@3.14.0
Manage agentic work across repositories with durable workbases
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe postinstall hook automatically installs a package-owned agent extension, which falls under the warning policy for agent extension lifecycle setup. Source inspection found ownership checks and no concrete attack chain supporting a block.
Decision evidence
public snapshot- The install lifecycle automatically runs the package-owned extension installer; uninstall also invokes its removal mode.
- The installer copies this package's Agency extension into the user's Pi agent extensions directory and tracks file ownership.
- Uninstallation removes the extension only when its ownership marker and content hash match.
- The inspected integration target identifies workbase-local agent and OpenCode configuration paths; no foreign broad agent-control mutation was established there.
- The installer skips an existing extension it cannot prove ownership of and only updates a matching owned copy.
- Integration configuration synchronization is exposed through a service method rather than shown as part of the npm install hook.
Source & flagged code
10 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.14.0.
See all versions of @markjaquith/agency for other recorded verdicts.
- Review the evidence and your use of @markjaquith/agency@3.14.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.