create-pmos@0.429.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 6d ago · by lpm-firewall-aiThe package is a CLI scaffold, with the network-using workspace activation documented as opt-in. The flagged credential and prompt flows are directed to GitHub’s own API or gated behind loopback routing, a saved key, repository consent, a routing switch, and secret scanning.
Decision evidence
public snapshot- The manifest exposes the package through the create-pmos CLI.
- The CLI describes file-mode scaffolding as making no network calls; installing the workspace is opt-in.
- The cockpit’s routing URL accepts only a loopback address supplied by the workspace.
- Prompt routing requires a saved key, repository consent, and a routing switch that defaults off; prompts that fail the secret scan are withheld.
- The installer sends GITHUB_TOKEN to GitHub’s API to retrieve Git for Windows release data.
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.429.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.429.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.