@markjaquith/agency@3.10.0
Manage agentic work across repositories with durable workbases
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe automatic setup installs a first-party agent extension that can influence agent context, which warrants a warning under the agent extension lifecycle policy. Its ownership checks and Agency-specific behavior do not establish a concrete attack.
Decision evidence
public snapshot- The postinstall hook runs the package-owned Pi extension installer.
- The installer places the extension in the user’s Pi agent extensions directory and only updates an existing file when its ownership marker and content hash match.
- The extension runs Agency context lookup and can add project instructions to an agent’s system prompt when a workbase is found.
- Integration inspection identifies the project’s `.agency/AGENTS.md` instructions file.
- The installer skips existing files it cannot prove it owns and does not follow symlinks for updates.
- The integration sync that manages project-level agent files is exposed through an explicit CLI subcommand.
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.10.0.
See all versions of @markjaquith/agency for other recorded verdicts.
- Review the evidence and your use of @markjaquith/agency@3.10.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.