create-pmos@0.486.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 flagged credential and network flows resolve to an optional prompt-routing feature with consent gates and secret-pattern filtering. Agent configuration is added by the user-run scaffolding command and points to the package’s bundled plugin.
Decision evidence
public snapshot- The CLI runs vendoring, updating, or workspace setup through explicit command branches; its default branch calls the vendoring function.
- Vendoring offers the cockpit plugin in the repository’s Claude settings, and the plugin’s marketplace and enablement entries point to the bundled PMOS directory.
- Prompt routing requires a saved key, repository consent, and the routing switch.
- Before routing, the workspace withholds prompts matching secret patterns or excluded paths; its documentation says prompt routing is off until enabled and describes what is sent.
- The TypeSafe endpoint is fixed in source at api.typesafe.ai/v1/systemone.
Source & flagged code
13 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.486.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.486.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.