kempo@4.2.39
A fullstack CMS framework for creating websites with user authentication
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the CLI’s process execution occurs during explicit project initialization. The flagged dynamic import serves request-selected route files, while inspected dependency install behavior is consistent with native addon setup.
Decision evidence
public snapshot- The package manifest lists build, database, admin and test scripts; it has no install lifecycle hook.
- The CLI exits unless the caller explicitly runs the init command, and installs Kempo as a setup step.
- The flagged middleware import loads a route file to handle a request.
- The inspected bcrypt install script runs node-gyp-build; dotenv and drizzle-kit show no install script, and drizzle-kit’s inspected entrypoint only exports defineConfig.
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.39.
See all versions of kempo for other recorded verdicts.
- Review the evidence and your use of kempo@4.2.39 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.