create-pmos@0.477.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-aiThe flagged shell execution and agent configuration relate to explicit CLI setup, while the reviewed prompt routing requires an enabled setting and a workspace-provided URL. The inspected source does not show unauthorized credential transfer or unrelated automatic activity.
Decision evidence
public snapshot- The package exposes a CLI entry point and has no lifecycle scripts in its manifest.
- Scaffolding and cockpit setup run through explicit CLI commands; the cockpit writes only a project-local Claude settings entry.
- Prompt routing requires a PMOS workspace URL, and sub-agent routing is gated by routing being on.
- The package describes itself as a local PM workflow kit and says the scaffolder makes no network calls.
- The cockpit sends prompts to the workspace-provided route URL; its code says the workspace holds the Jev key and the mod does not see it.
Source & flagged code
13 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.477.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.477.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.