@desplega.ai/agent-fs@0.12.0
Agent-first filesystem backed by S3
AI Security Review
scanned 3mo ago · by lpm-firewall-aiScanner findings conflate documented, user-configured storage and embedding traffic with credential exfiltration. Source inspection found no install-time execution or unconsented collection/exfiltration chain.
Decision evidence
public snapshot- dist/cli.js can send configured file content to S3 and selected embedding providers.
- dist/cli.js runs Docker/FUSE helpers only through explicit onboard or mount commands.
- package.json has no preinstall/install/postinstall hook; prepublishOnly is publish-time build only.
- CLI entrypoint requires an explicit user command; imports do not start network activity.
- Remote API URL and API key come from explicit flags, AGENT_FS_* variables, or its own config.
- Embedding clients use user-supplied OpenAI/Gemini keys for the documented semantic-search feature.
- FUSE helper is hash-checked against dist/fuse-bin.manifest.json before spawning.
- No eval/new Function, arbitrary payload download, or AI-agent configuration writes found.
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 · L173Findings
Affected versions and remediation
This report applies to @desplega.ai/agent-fs@0.12.0.
See all versions of @desplega.ai/agent-fs for other recorded verdicts.
- Review the evidence and your use of @desplega.ai/agent-fs@0.12.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.