create-pmos@0.482.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 3d ago · by lpm-firewall-aiThe package has no lifecycle scripts, and its CLI performs scaffolding when explicitly invoked. Prompt routing is an intended feature, gated by a saved key, repository consent, a switch that defaults off, and secret and path checks.
Decision evidence
public snapshot- Prompt routing requires a saved key, repository consent, and a separate switch that defaults off; prompts flagged by the secret scan or excluded paths are withheld.
- The plugin accepts only the workspace-provided loopback routing URL.
- The CLI vendors the bundled kit when explicitly run; its Claude settings entry offers the package’s own plugin from the local pmos/mods directory.
- The package manifest describes a scaffolding CLI and exposes bin/create-pmos.js; no lifecycle scripts are present.
- When routing is enabled, the workspace may send a prompt for classification, which is part of the package’s prompt-routing feature.
Source & flagged code
12 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.482.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.482.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.