kempo@4.5.4
A fullstack CMS framework for creating websites with user authentication
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package has no install hook, and the risky operations are reachable through its explicit setup command. Automatic deletion of a matching database volume without a separate volume-specific confirmation remains a significant destructive risk, so warn rather than block.
Decision evidence
public snapshot- The package exposes `bin/cli.js` as its `kempo` command, which accepts the explicit `init` action.
- When initializing a new container, the CLI stops and removes the named Docker container and deletes the corresponding named volume before recreating it; existing database data can be lost.
- The CLI also removes the project’s migration directory before running a forced schema push.
- The manifest declares no install lifecycle hook; the destructive behavior is in the explicitly invoked setup command.
- The CLI asks before deleting listed project files when reinitializing an existing project, but that confirmation does not cover the Docker volume deletion.
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.5.4.
See all versions of kempo for other recorded verdicts.
- Review the evidence and your use of kempo@4.5.4 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.