eve@0.45.1
Filesystem-first framework for durable backend AI agents that run anywhere.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiAn aliased dependency on an older release of the same package is a real supply-chain risk that cannot be treated as ordinary metadata. The current release has no install hook or source-grounded malicious action, so blocking is not justified.
Decision evidence
public snapshot- The manifest installs eve version 0.30.8 again under an alias, creating a nested older-release supply-chain path.
- The package exposes agent-facing shell, file-read, and file-write tools, so an application using it can grant broad workspace capabilities.
- The CLI can spawn commands, although this occurs when the user invokes the CLI rather than during installation.
- package.json contains no preinstall, install, postinstall, or prepare lifecycle hook.
- The inspected manifest does not directly depend on its own current release name.
- No unsolicited credential exfiltration, destructive action, or remote payload execution was established from inspected source.
Source & flagged code
20 flagged · loading sourceSource spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
bin/eve.jsView on unpkg · L2Package source references dynamic require/import behavior.
bin/eve.jsView on unpkg · L8Findings
Affected versions and remediation
This report applies to eve@0.45.1.
See all versions of eve for other recorded verdicts.
- Review the evidence and your use of eve@0.45.1 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.