create-pmos@0.437.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 local prompt-routing bridge, not automatic credential transmission. External classification requires a saved key, repository consent, and the routing switch, and the service host is fixed in source.
Decision evidence
public snapshot- The cockpit hook accepts only the workspace-provided loopback URL for prompt routing.
- The workspace requires a saved key, repository consent, and the separate routing switch before sending a prompt; secret-scanned and excluded prompts are withheld.
- The outbound classifier host is fixed as api.typesafe.ai, and the source says redirects are refused.
- Turning routing on requires the user's own typed command.
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.437.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.437.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.