registry / @markjaquith/agency / 3.19.0
@markjaquith/agency@3.19.0
Manage agentic work across repositories with durable workbases
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe automatic postinstall installs a first-party agent extension, which is a guarded agent-extension lifecycle risk under the review policy. The source shows ownership checks for existing files and no concrete malicious behavior in the inspected paths.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Installing the package through npm runs its postinstall hook.
Impact
The extension becomes available to the user’s Pi agent. No credential access or exfiltration was established from the inspected evidence.
Mechanism
The hook copies the bundled extension into the user’s Pi agent extensions directory; existing files are protected unless ownership can be verified.
AI rationale
The automatic postinstall installs a first-party agent extension, which is a guarded agent-extension lifecycle risk under the review policy. The source shows ownership checks for existing files and no concrete malicious behavior in the inspected paths.
Evidence
package.jsonscripts/install-pi-extension.ts~/.pi/agent/extensions/agency.ts
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The postinstall hook automatically runs the extension installer.
- The installer targets the user’s Pi agent extensions directory.
- Installation creates the destination directory and copies the bundled extension when no file exists there.
- Uninstall removes the extension only when its ownership hash matches.
- Integration inspection also targets project-level agent and OpenCode configuration paths.
Evidence against
- The installer skips an existing destination it cannot verify as package-managed.
- No evidence inspected here shows credential collection, exfiltration, or a broader agent-control write.
Behavioral surface
CryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
8 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = bun scripts/install-pi-extension.ts install
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = bun scripts/install-pi-extension.ts install
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgsrc/utils/interactive-loader.tsView file
3const preload = ["@opentui", "solid", "preload"].join("/")
L4: await import(preload)
L5: return import("./interactive")
Medium
Dynamic Require
Package source references dynamic require/import behavior.
src/utils/interactive-loader.tsView on unpkg · L3Findings
4 High7 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitednode_modules/@babel/core/lib/config/files/plugins.js#virtual:normalized:round1
HighKnown Malware Source Similaritysrc/utils/process.ts
HighPrevious Version Dangerous Deltasrc/services/ReviewService.ts
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiresrc/utils/interactive-loader.ts
MediumNetwork
MediumEnvironment Vars
MediumShips Native Binarynode_modules/@opentui/core-linux-x64/libopentui.so
MediumShips Wasm Modulenode_modules/@opentui/core/assets/zig/tree-sitter-zig.wasm
MediumStructural Risk Force Deep Review
Low
Affected versions and remediation
This report applies to @markjaquith/agency@3.19.0.
See all versions of @markjaquith/agency for other recorded verdicts.
- Review the evidence and your use of @markjaquith/agency@3.19.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.