registry / create-pmos / 0.462.0

create-pmos@0.462.0

Scaffold the PMOS portable kit — run the PMOS product-management workflow (initiative → lane-fit spec → contract → build → three gates, with work-type lanes for features, research, maintenance, incidents, and content) entirely inside your own repo, with a

AI Security Review

scanned 5d ago · by lpm-firewall-ai

The package has no npm lifecycle scripts, and its entry point dispatches work from explicit CLI arguments. The flagged prompt and credential flows are scoped to local or intended AI services, with external Jev routing gated by saved-key, consent, and opt-in settings.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

The user runs the CLI or its separately documented setup command; workspace activation requires the workspace subcommand.

Impact

Expected local setup and application behavior; no unauthorized credential or project-data transfer was identified.

Mechanism

The CLI writes the requested kit and offers local Claude Code settings. Optional prompt routing goes through loopback and contacts Jev only after its key, consent, and routing gates are enabled.

AI rationale

Evidence

pmos/.pmos-profile.gitattributes.claude/settings.json.claude/skills/*

Decision evidence

public snapshot

AI called this Clean at 94.0% confidence as Benign with medium false-positive risk.

Evidence for AI clean decision

The manifest exposes a CLI and defines no npm lifecycle scripts.
The CLI selects scaffold, update, or workspace actions from explicit command arguments.
The scaffold offers a local Claude Code mod through additive repository settings; the project must still be trusted in Claude Code.
Prompt routing uses a loopback workspace address, and the mod does not receive the Jev key.
Sending prompts to Jev requires a saved key, repository consent, and routing enabled; routing is off by default and prompts are screened for secrets.
The workspace’s Claude API loop uses ANTHROPIC_API_KEY for its own API call and removes it from the environment passed to child commands.

Evidence against

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket

Supply chain

HighEntropyStringsMinified

Source & flagged code

11 flagged

workspace/premium-viewer-share-test.jsView file

61patternName = generic_password severity = medium line = 61

Medium

Secret Pattern

Package contains a possible secret pattern.

workspace/premium-viewer-share-test.jsView on unpkg · L61

bin/create-pmos.jsView file

23const path = require('path'); L24: const { spawnSync } = require('child_process'); L25:

High

Child Process

Package source references child process execution.

bin/create-pmos.jsView on unpkg · L23

181const probe = process.platform === 'win32' ? `where ${cmd}` : `command -v ${cmd}`; L182: try { return spawnSync(probe, { stdio: 'ignore', shell: true }).status === 0; } L183: catch { return false; }

High

Shell

Package source references shell execution.

bin/create-pmos.js

Findings

1 Critical6 High6 Medium5 Low

CriticalCredential Exfiltrationpayload/mods/pmos-cockpit/hooks/register.tsx

HighChild Processbin/create-pmos.js

HighShellbin/create-pmos.js

HighSame File Env Network Executionworkspace/premium-chat-chart-tab-test.js

HighCommand Output Exfiltrationworkspace/server.js

HighTrigger Reachable External Ai Agent Control Surface Mutationbin/create-pmos.js

HighSemantic Analysis Limitedbin/create-pmos.js#virtual:normalized:round1

MediumSecret Patternworkspace/premium-viewer-share-test.js

MediumDynamic Requirebin/create-pmos.js

MediumNetwork

MediumEnvironment Vars

MediumShips Build Helper

Affected versions and remediation

This report applies to create-pmos@0.462.0.

See all versions of create-pmos for other recorded verdicts.

Review the evidence and your use of create-pmos@0.462.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: 2026-10-31 02:31:38.894Z (UTC).

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

registry / create-pmos / 0.462.0

create-pmos@0.462.0

AI Security Review

scanned 5d ago · by lpm-firewall-ai

Static reason

High-risk behavior combination matched malicious policy.

Trigger

The user runs the CLI or its separately documented setup command; workspace activation requires the workspace subcommand.

Impact

Expected local setup and application behavior; no unauthorized credential or project-data transfer was identified.

Mechanism

The CLI writes the requested kit and offers local Claude Code settings. Optional prompt routing goes through loopback and contacts Jev only after its key, consent, and routing gates are enabled.

AI rationale

Evidence

pmos/.pmos-profile.gitattributes.claude/settings.json.claude/skills/*

Decision evidence

public snapshot

AI called this Clean at 94.0% confidence as Benign with medium false-positive risk.

Evidence for AI clean decision

The manifest exposes a CLI and defines no npm lifecycle scripts.
The CLI selects scaffold, update, or workspace actions from explicit command arguments.
The scaffold offers a local Claude Code mod through additive repository settings; the project must still be trusted in Claude Code.
Prompt routing uses a loopback workspace address, and the mod does not receive the Jev key.
Sending prompts to Jev requires a saved key, repository consent, and routing enabled; routing is off by default and prompts are screened for secrets.
The workspace’s Claude API loop uses ANTHROPIC_API_KEY for its own API call and removes it from the environment passed to child commands.

Evidence against

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket

Supply chain

HighEntropyStringsMinified

Source & flagged code

11 flagged

workspace/premium-viewer-share-test.jsView file

61patternName = generic_password severity = medium line = 61

Medium

Secret Pattern

Package contains a possible secret pattern.

workspace/premium-viewer-share-test.jsView on unpkg · L61

bin/create-pmos.jsView file

23const path = require('path'); L24: const { spawnSync } = require('child_process'); L25:

High

Child Process

Package source references child process execution.

bin/create-pmos.jsView on unpkg · L23

High

Shell

Package source references shell execution.

bin/create-pmos.js

Findings

1 Critical6 High6 Medium5 Low

CriticalCredential Exfiltrationpayload/mods/pmos-cockpit/hooks/register.tsx

HighChild Processbin/create-pmos.js

HighShellbin/create-pmos.js

HighSame File Env Network Executionworkspace/premium-chat-chart-tab-test.js

HighCommand Output Exfiltrationworkspace/server.js

HighTrigger Reachable External Ai Agent Control Surface Mutationbin/create-pmos.js

HighSemantic Analysis Limitedbin/create-pmos.js#virtual:normalized:round1

MediumSecret Patternworkspace/premium-viewer-share-test.js

MediumDynamic Requirebin/create-pmos.js

MediumNetwork

MediumEnvironment Vars

MediumShips Build Helper

Affected versions and remediation

This report applies to create-pmos@0.462.0.

See all versions of create-pmos for other recorded verdicts.

Review the evidence and your use of create-pmos@0.462.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: 2026-10-31 02:31:38.894Z (UTC).

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