create-pmos@0.465.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 5d ago · by lpm-firewall-aiThe flagged credential and network behavior serves the workspace’s prompt-routing feature and is gated by a saved key, repository consent, and a default-off switch. Project-local plugin setup occurs as part of the user-invoked scaffolding command.
Decision evidence
public snapshot- The package exposes a CLI for explicit kit vending, updates, and optional workspace activation.
- The CLI’s project settings change registers the bundled pmos-cockpit plugin and marketplace.
- External prompt routing requires a saved key, repository consent, and a routing switch that defaults off; prompts failing the secret scan or matching excluded paths are withheld.
- The cockpit hook sends prompt text and repository root to the workspace’s loopback endpoint; it does not receive the routing key.
- The workspace’s external routing endpoint is fixed to api.typesafe.ai, and it refuses redirects.
Source & flagged code
11 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.465.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.465.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.