create-pmos@0.492.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 reviewed source supports the package’s scaffolding and optional local workspace purpose. The flagged prompt-routing code uses a workspace-provided loopback URL, and workspace installation is gated by an explicit subcommand; no concrete attack behavior was found.
Decision evidence
public snapshot- The package describes itself as a scaffold and lists a CLI entry point; workspace activation is a distinct subcommand.
- The cockpit setup adds its marketplace and plugin entry to the target repository’s Claude settings, preserving existing values.
- The routing hook uses a URL supplied through the workspace environment and says it sends prompts only to the loopback address; without that environment value, it makes no request.
- The package CLI dispatches workspace installation only when the user supplies the `workspace` subcommand.
Source & flagged code
14 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.492.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.492.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.