kempo@4.2.38
A fullstack CMS framework for creating websites with user authentication
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe CLI’s volume removal is part of an explicitly invoked setup flow, but it can remove a matching Docker volume without confirming ownership or warning about its contents. This supports a warning for unresolved destructive risk, not a confirmed malicious attack.
Decision evidence
public snapshot- The package exposes a CLI that proceeds when the user invokes its init command.
- In new-container mode, the CLI removes a Docker volume named from the database name before starting Docker Compose; the removal is not confirmed in this path.
- The destructive behavior is limited to the explicitly invoked project initializer and its new-container setup path.
Source & flagged code
6 flagged · loading sourceThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
bin/cli.jsView on unpkgFindings
Affected versions and remediation
This report applies to kempo@4.2.38.
See all versions of kempo for other recorded verdicts.
- Review the evidence and your use of kempo@4.2.38 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.