@desplega.ai/agent-fs@0.13.7
Agent-first filesystem backed by S3
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection shows a user-run CLI with publisher-only scripts and first-party local config, not an install-time attack. Shell, network, and native helper use stay inside explicit agent-fs commands and caller-supplied endpoints.
Decision evidence
public snapshot- package.json defines no preinstall, install, or postinstall hook; the only script is prepublishOnly for the publisher build.
- The agent-fs bin entry points at dist/cli.js, which starts only when a user runs the CLI.
- Runtime state is written under AGENT_FS_HOME or ~/.agent-fs, including config.json, and the default server binds to 127.0.0.1.
- Optional fuse packages are same-vendor, version-pinned native helpers, not a runtime dependency on this package name.
- child_process and fetch appear only inside user-invoked CLI paths such as onboard, the fuse helper, and the caller-configured API client.
- No code writes foreign agent config files such as Claude or Cursor settings, and no credential is sent to a hidden package-controlled host.
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.7.
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.7 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.