create-pmos@0.503.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 2d ago · by lpm-firewall-aiThe package has no npm lifecycle scripts, and the flagged configuration changes occur when the user invokes the scaffolder. The cockpit's prompt routing requires a URL supplied by the workspace and uses that configured service path.
Decision evidence
public snapshot- The manifest describes a PMOS scaffolding tool and declares no npm lifecycle scripts.
- The CLI adds the kit's skills and offers its cockpit mod through repository settings when the user runs the scaffolder.
- The cockpit route helper uses PMOS_ROUTE_URL and returns without making a request when that variable is absent.
- The route request sends the session root and prompt to that configured URL; the source says the workspace holds the service key and the mod does not see it.
- The shell and PowerShell installers document downloading and installing PMOS and its stated prerequisites when the user runs them.
Source & flagged code
25 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.503.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.503.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.