registry / create-pmos / 0.458.0

create-pmos@0.458.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 6d ago · by lpm-firewall-ai

The package has no install lifecycle hook, and the routed credential and network findings are explained by optional workspace behavior and synthetic test fixtures. Prompt routing is restricted to a loopback bridge and external classification requires the saved key, repository consent, and routing gates.

Static reason

High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source

Trigger

Prompt routing requires a saved key, repository consent, and the routing switch; the scaffold CLI has no lifecycle hook.

Impact

No unauthorized credential transfer or other attack behavior was identified.

Mechanism

The cockpit sends prompts to a validated loopback workspace URL. The workspace may then classify prompts through api.typesafe.ai after checking its gates and secret scan.

AI rationale

Network endpoints2

api.typesafe.ai/v1/systemone127.0.0.1:<workspace-port>/api/model/route

Decision evidence

public snapshot

AI called this Clean at 95.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

The manifest has no lifecycle scripts; it exposes a CLI entry point.
The CLI describes scaffolding as network-free and the workspace GUI as an opt-in command.
The cockpit hook accepts only a loopback workspace route URL.
Prompt text reaches the external classifier only when the saved-key, repository-consent, and routing gates are open; secret-matched or excluded prompts are withheld.
A scanner-hit test uses a synthetic AWS key and asserts that sharing is refused without exposing the key.

Evidence against

The workspace can send user prompts to api.typesafe.ai for classification when the user enables routing and repository consent.

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket

Supply chain

HighEntropyStringsMinifiedTelemetryUrlStrings

Source & flagged code

12 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

2 Critical6 High6 Medium5 Low

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

CriticalPrevious Version Dangerous Deltaworkspace/adler-moments-test.js

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

Affected versions and remediation

This report applies to create-pmos@0.458.0.

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

Review the evidence and your use of create-pmos@0.458.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-30 04:07:44.577Z (UTC).

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

registry / create-pmos / 0.458.0

create-pmos@0.458.0

AI Security Review

scanned 6d ago · by lpm-firewall-ai

Static reason

High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source

Trigger

Prompt routing requires a saved key, repository consent, and the routing switch; the scaffold CLI has no lifecycle hook.

Impact

No unauthorized credential transfer or other attack behavior was identified.

Mechanism

The cockpit sends prompts to a validated loopback workspace URL. The workspace may then classify prompts through api.typesafe.ai after checking its gates and secret scan.

AI rationale

Network endpoints2

api.typesafe.ai/v1/systemone127.0.0.1:<workspace-port>/api/model/route

Decision evidence

public snapshot

AI called this Clean at 95.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

The manifest has no lifecycle scripts; it exposes a CLI entry point.
The CLI describes scaffolding as network-free and the workspace GUI as an opt-in command.
The cockpit hook accepts only a loopback workspace route URL.
Prompt text reaches the external classifier only when the saved-key, repository-consent, and routing gates are open; secret-matched or excluded prompts are withheld.
A scanner-hit test uses a synthetic AWS key and asserts that sharing is refused without exposing the key.

Evidence against

The workspace can send user prompts to api.typesafe.ai for classification when the user enables routing and repository consent.

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket

Supply chain

HighEntropyStringsMinifiedTelemetryUrlStrings

Source & flagged code

12 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

2 Critical6 High6 Medium5 Low

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

CriticalPrevious Version Dangerous Deltaworkspace/adler-moments-test.js

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

Affected versions and remediation

This report applies to create-pmos@0.458.0.

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

Review the evidence and your use of create-pmos@0.458.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-30 04:07:44.577Z (UTC).

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