kempo@4.6.0
A fullstack CMS framework for creating websites with user authentication
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe scanner’s runtime installation signal is part of the user-invoked project setup flow. However, that flow can remove a matching Docker volume without a specific confirmation, so the data-loss risk warrants a warning.
Decision evidence
public snapshot- The CLI is activated by a user running its init command; it also installs Kempo into the selected project during setup.
- When setup creates a new database container, it stops and removes a container with the selected name and removes the correspondingly named Docker volume. The noninteractive mode skips the existing-container selection prompt, so prior database data could be removed without a specific warning.
- For an existing project with a public directory, noninteractive mode exits; interactive reinitialization asks for confirmation before deleting listed project files.
- The destructive behavior is confined to the setup CLI and is not an install-time package lifecycle action.
- Interactive setup lets the user review existing containers and explicitly confirms reinitialization of an existing project. These safeguards do not specifically confirm removal of a matching Docker volume.
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.6.0.
See all versions of kempo for other recorded verdicts.
- Review the evidence and your use of kempo@4.6.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.