registry / create-pmos / 0.475.0

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

The package's shell execution and agent configuration are part of its scaffold and local workspace setup. Prompt routing is user-enabled and sends requests through the workspace's loopback interface, with the routing key kept server-side.

Static reason

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

Trigger

Workspace setup requires the explicit `workspace` command; prompt routing requires the user's typed `/pmos-route on` command.

Impact

No malicious credential transfer, unrelated automatic action, or concealed execution was identified.

Mechanism

The CLI scaffolds the bundled kit and can register its cockpit extension. When routing is enabled in a workspace terminal, the mod asks the local workspace for a route without handling its key.

AI rationale

Decision evidence

public snapshot

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

Evidence for AI clean decision

The package describes itself as a PMOS workflow scaffold and local workspace app.
The CLI documents workspace dependency installation as an explicit opt-in subcommand.
Prompt routing uses a loopback URL from the workspace; the mod does not receive the Jev key.
Routing can be enabled only by the user's typed `/pmos-route on` command.
Claude readiness checks are explicitly described as not returning or persisting credentials or CLI output.

Evidence against

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket

Supply chain

HighEntropyStringsMinifiedTelemetryUrlStrings

ManifestNo manifest risk signals triggered.

scanned 879 file(s), 14.4 MB of source, external domains: 127.0.0.1, acme.atlassian.net, acme.slack.com, app.amplitude.com, auth0.com, boards.example.com, boards.pm-os.app, boards.test, docs.google.com, docs.npmjs.com, docs.stripe.com, drive.example, evil.example, example.atlassian.net, example.com, github.com, huggingface.co, jira.example, jira.example.com, mail.example, mcp.atlassian.com, mcp.slack.com, meet.google.com, pmos-menus.test, purl.org, regulator.example, rivalnotes.example, schemas.openxmlformats.org, share.example, share.invalid, slack.example, slack.example.com, upgrade.invalid, wiki.example, wiki.example.com, www.apple.com, www.w3.org, x.atlassian.net, x.example

Source & flagged code

13 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 High7 Medium5 Low

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

CriticalPrevious Version Dangerous Deltaworkspace/lib/claude-readiness.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.475.0.

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

Review the evidence and your use of create-pmos@0.475.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-11-01 06:23:52.131Z (UTC).

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

registry / create-pmos / 0.475.0

create-pmos@0.475.0

AI Security Review

scanned 4d ago · by lpm-firewall-ai

Static reason

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

Trigger

Workspace setup requires the explicit `workspace` command; prompt routing requires the user's typed `/pmos-route on` command.

Impact

No malicious credential transfer, unrelated automatic action, or concealed execution was identified.

Mechanism

The CLI scaffolds the bundled kit and can register its cockpit extension. When routing is enabled in a workspace terminal, the mod asks the local workspace for a route without handling its key.

AI rationale

Decision evidence

public snapshot

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

Evidence for AI clean decision

The package describes itself as a PMOS workflow scaffold and local workspace app.
The CLI documents workspace dependency installation as an explicit opt-in subcommand.
Prompt routing uses a loopback URL from the workspace; the mod does not receive the Jev key.
Routing can be enabled only by the user's typed `/pmos-route on` command.
Claude readiness checks are explicitly described as not returning or persisting credentials or CLI output.

Evidence against

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket

Supply chain

HighEntropyStringsMinifiedTelemetryUrlStrings

ManifestNo manifest risk signals triggered.

Source & flagged code

13 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 High7 Medium5 Low

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

CriticalPrevious Version Dangerous Deltaworkspace/lib/claude-readiness.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.475.0.

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

Review the evidence and your use of create-pmos@0.475.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-11-01 06:23:52.131Z (UTC).

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