kempo@4.3.0
A fullstack CMS framework for creating websites with user authentication
AI Security Review
scanned 2d ago · by lpm-firewall-aiThis is a conditional destructive capability in a user-invoked initializer, so warn rather than block. The inspected source does not establish automatic install-time attack behavior.
Decision evidence
public snapshot- The manifest lists build, database, and test scripts, with no package install lifecycle hook.
- The CLI setup flow runs only for the initializer command; its yes option selects defaults.
- Cleanup uses project-derived Docker names and removes the matching database volume before starting the stack.
- For an existing project, interactive reinitialization asks before deleting listed files, but the prompt does not mention the database volume.
- This risk is in a user-invoked project setup flow, rather than an automatic package install hook.
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.3.0.
See all versions of kempo for other recorded verdicts.
- Review the evidence and your use of kempo@4.3.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.