create-pmos@0.474.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 source matches the package’s scaffolding and local-workspace purpose. Its prompt-routing path is gated by user-controlled settings and sends requests only to the fixed TypeSafe service endpoint.
Decision evidence
public snapshot- The package is a CLI for scaffolding a PMOS kit and optionally launching its local workspace GUI.
- The CLI dispatches work from explicit user-supplied commands such as vendor, update, and workspace.
- Prompt routing requires an enabled policy and all routing gates; the settings source says routing defaults off and requires a key, repository consent, and the route switch.
- When routing is enabled, the classifier uses the fixed api.typesafe.ai endpoint; the API key is required and is not sent when absent.
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.474.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.474.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.