create-pmos@0.404.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 12d ago · by lpm-firewall-aiThe manifest has no install lifecycle scripts, and the reviewed configuration change is first-party setup performed by the explicitly invoked CLI. The scanner’s credential finding resolves to a test of secret rejection, while prompt routing is restricted to the local workspace.
Decision evidence
public snapshot- The manifest exposes a CLI entry point and defines no lifecycle scripts; the bundled kit is copied when the user runs the vendor command.
- That command offers the first-party cockpit plugin through project settings. The installer adds missing local marketplace and plugin keys while preserving existing values.
- Prompt routing accepts only the workspace-provided loopback address and sends prompts to that local route when configured.
- The apparent secret transfer is a test: it submits a fixture containing a fake key and checks that the share endpoint rejects it without returning the key text.
- The other flagged paths concern local workspace features, tests, UI rendering and guarded repository workflows; no separate attack behavior was identified.
- The explicit scaffold command can enable the first-party plugin in the project’s Claude settings.
- The plugin’s session routing is enabled by default, but it only contacts a configured local workspace endpoint.
Source & flagged code
11 flaggedPackage contains a possible secret pattern.
workspace/premium-viewer-share-test.jsView on unpkg · L61Package source references child process execution.
bin/create-pmos.jsView on unpkg · L23Package source references shell execution.
bin/create-pmos.jsFindings
Affected versions and remediation
This report applies to create-pmos@0.404.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.404.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.