registry / Destructive action / kempo / 4.5.2

kempo@4.5.2

A fullstack CMS framework for creating websites with user authentication

AI Security Review

scanned 2d ago · by lpm-firewall-ai

Source inspection found no lifecycle hook or evidence of credential theft or covert network behavior. The init command can nevertheless delete a matching Docker volume, so warn about the conditional data-loss risk rather than block publication.

Static reason

One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source

Trigger

A user runs the kempo init command in a project directory where the CLI selects an existing container or volume name.

Impact

The removed database volume may contain data that cannot be recovered from that volume.

Mechanism

The CLI runs Docker stop and remove commands for the selected container and removes the volume derived from the database name, then starts Compose.

AI rationale

Evidence

bin/cli.js

Decision evidence

public snapshot

AI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.

Evidence for warning

The package exposes bin/cli.js as its kempo command, which accepts an explicit init command.
During init, the CLI derives a container and volume name from the project or database name, then stops and removes the container and removes that named Docker volume before starting Compose.
The CLI has a confirmation step for reinitializing an existing Kempo project; with the yes flag, it exits when that project’s public directory exists.

Evidence against

The manifest declares no preinstall, install, or postinstall lifecycle hook; the flagged actions are part of the explicit CLI setup flow.
The inspected CLI excerpts show project scaffolding and local Docker setup, with no evidence of credential collection or unrelated network transfer.

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell

Supply chain

HighEntropyStrings

Source & flagged code

6 flagged

bin/cli.jsView file

Lines 1-25javascript

1#!/usr/bin/env node

3import { existsSync, cpSync, mkdirSync, writeFileSync, rmSync } from 'fs';

4import { fileURLToPath, pathToFileURL } from 'url';

5import { join, dirname, basename } from 'path';

6import { execSync, spawnSync } from 'child_process';

7import crypto from 'crypto';

High

Child Process

Package source references child process execution.

bin/cli.jsView on unpkg · L5

8import inquirer from 'inquirer';

10const args = process.argv.slice(2);

11const command = args[0];

12const useDefaults = args.includes('-y') || args.includes('--yes');

14if(command !== 'init'){

15 console.log('Usage: npx kempo init [-y|--yes]');

16 process.exit(1);

17}

19const __filename = fileURLToPath(import.meta.url);

20const __dirname = dirname(__filename);

21const moduleRoot = join(__dirname, '..');

22const projectDir = process.cwd();

23const projectName = basename(projectDir);

25/*

High

Entrypoint Build Divergence

Manifest entrypoint contains risky behavior absent from dist/build output.

bin/cli.jsView on unpkg · L5

Lines 391-458javascript

391

392writeFileSync(join(projectDir, '.env'),

393`# Database

394DATABASE_URL=${databaseUrl}

395

396# Email${emailServiceSkipped ? '\n# Configure your email service — update the values below' : ''}

397RESEND_API_KEY=${

•matchType = previous_version_dangerous_delta matchedPackage = kempo@4.2.22 matchedIdentity = npm:a2VtcG8:4.2.22 similarity = 0.658 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 unpkg

middleware/kempo.jsView file

Lines 82-122javascript

82 return { filePath: join(base, head), params: {} };

83 }

84 }

85 if(rest.length === 0){

86 for(const entry

Source & flagged code

6 flagged · loading source

bin/cli.jsView 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 unpkg

5import { join, dirname, basename } from 'path'; L6: import { execSync, spawnSync } from 'child_process'; L7: import crypto from 'crypto';

High

Child Process

Package source references child process execution.

bin/cli.jsView on unpkg · L5

438stdio: 'inherit', L439: shell: true L440: });

High

Shell

Package source references shell execution.

bin/cli.jsView on unpkg · L438

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.5.2.

See all versions of kempo for other recorded verdicts.

Review the evidence and your use of kempo@4.5.2 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: 2026-10-21 04:04:49.562Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.