kempo@4.6.2
A fullstack CMS framework for creating websites with user authentication
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package has no automatic install hook, but its exposed setup command performs unconfirmed deletion of a named Docker volume. That destructive effect supports blocking publication.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs kempo init with Docker available; --yes selects the new-container defaults without prompting about existing containers.
Impact
An existing container and its database volume may be deleted without confirmation, causing data loss.
Mechanism
The CLI derives the container and database names from the project directory, then stops and removes that container and removes the corresponding Docker volume before starting Compose.
Attack narrative
Running the setup command with defaults can remove a Docker container and its project-named database volume without asking before deletion. This creates a direct risk of losing existing database data.
AI rationale
The package has no automatic install hook, but its exposed setup command performs unconfirmed deletion of a named Docker volume. That destructive effect supports blocking publication.
Evidence
bin/cli.js
Decision evidence
public snapshotAI called this Malicious at 91.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package exposes bin/cli.js as the kempo command.
- The CLI treats --yes as setup defaults and uses the current project directory name for the new database and container.
- During new-container setup, the CLI stops and removes the named container and removes its matching Docker volume without a deletion confirmation.
Evidence against
- package.json declares no preinstall, install, or postinstall hook; the destructive path requires running the CLI.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
6 flagged · loading sourcebin/cli.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = kempo@4.2.22
matchedIdentity = npm:a2VtcG8:4.2.22
similarity = 0.550
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
bin/cli.jsView on unpkg5import { join, dirname, basename } from 'path';
L6: import { execSync, spawnSync } from 'child_process';
L7: import crypto from 'crypto';
High
438stdio: 'inherit',
L439: shell: true
L440: });
High
5Manifest entrypoint (manifest.bin) carries capability families absent from dist/build output: environment+network, execution+network
L5: import { join, dirname, basename } from 'path';
L6: import { execSync, spawnSync } from 'child_process';
L7: import crypto from 'crypto';
...
L19: const __filename = fileURLToPath(import.meta.url);
L20: const __dirname = dirname(__filename);
L21: const moduleRoot = join(__dirname, '..');
...
L25: /*
L26: package.json
L27: */
...
L65: const waitForPostgres = async (containerName, dbName = 'postgres') => {
L66: process.stdout.write('Waiting for Postgres to be ready');
L67: for(let i = 0; i < 30; i++){
Findings
1 Critical4 High4 Medium4 Low
CriticalPrevious Version Dangerous Deltabin/cli.js
HighChild Processbin/cli.js
HighShellbin/cli.js
HighEntrypoint Build Divergencebin/cli.js
HighRuntime Package Installbin/cli.js
MediumDynamic Requiremiddleware/kempo.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to kempo@4.6.2.
See all versions of kempo for other recorded verdicts.
- Avoid installing kempo@4.6.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.