create-pmos@0.418.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 flow is a prompt-routing request to the local workspace, not credential transmission to a foreign host. Remote prompt classification is gated by a saved key, repository consent, and a switch that defaults off, with secret scanning and exclusions before sending.
Decision evidence
public snapshot- The CLI vendors its bundled PMOS payload when the user runs the command.
- The cockpit hook sends routing requests to a loopback workspace URL; the hook does not handle the Jev key.
- Prompt text is sent to Jev only when a key, repository consent, and the routing switch are all present; the switch defaults off.
- The router withholds prompts that match its secret scan or excluded paths.
- The external classifier endpoint is fixed in source to api.typesafe.ai/v1/systemone.
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.418.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.418.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.