@desplega.ai/agent-fs@0.13.9
Agent-first filesystem backed by S3
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection of package.json and the minified CLI shows no install hook, no foreign agent-config writes, and no hidden exfiltration sink. Vendor telemetry and docker or fuse process use are user-invoked or opt-out product behavior.
Decision evidence
public snapshot- package.json 0.13.9 publishes the agent-fs bin at dist/cli.js and only a prepublishOnly build script, with no npm install lifecycle hooks.
- The CLI sends product telemetry only when ANONYMIZED_TELEMETRY and DO_NOT_TRACK do not disable it, and the destination is the vendor host proxy.desplega.sh.
- The only shell execution found is a user-invoked onboard command that checks for a local docker binary.
- Optional same-vendor fuse helpers are hash-checked before spawn, and the daemon respawns this package's own server entry only after an explicit daemon start.
- Telemetry properties are usage counts, storage and embedding provider names, OS, and architecture, not API keys or file contents.
Source & flagged code
8 flaggedA single source file combines environment access, network access, and code or shell execution with blocking evidence.
dist/cli.jsView on unpkg · L223Findings
Affected versions and remediation
This report applies to @desplega.ai/agent-fs@0.13.9.
See all versions of @desplega.ai/agent-fs for other recorded verdicts.
- Review the evidence and your use of @desplega.ai/agent-fs@0.13.9 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.