create-pmos@0.446.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 flagged credential flows are bounded to their intended services: prompt routing is gated by saved-key and repository consent settings, and the installer sends a GitHub token to GitHub’s own API. The CLI behavior is tied to explicit user commands, with no malicious automatic action identified.
Decision evidence
public snapshot- The package exposes a create-pmos CLI; its argument dispatch selects workspace, update, or default vendor behavior.
- Cockpit prompt routing passes eligible submitted prompts to the local workspace only when routing is enabled.
- The workspace’s Jev route requires a saved key, repository consent, and a route switch that defaults off; the TypeSafe host is fixed in source.
- The installer uses GITHUB_TOKEN for a release lookup at GitHub’s own API host.
- No malicious behavior was identified in the reviewed flows.
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.446.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.446.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.