create-pmos@0.430.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 package's entry point is an explicitly invoked CLI, with no install lifecycle script. Its only examined outbound prompt flow is disclosed, constrained to a fixed service, and gated by repository consent and an opt-in routing switch.
Decision evidence
public snapshot- The package exposes a CLI entry point; the source has no install lifecycle script.
- The CLI selects its action from explicit command-line arguments, such as vendoring a kit or activating the workspace.
- Cockpit prompt routing requires a workspace-provided loopback URL; terminals without it make no routing request.
- The workspace sends prompts to Jev only with a saved key, repository consent, and routing switch enabled; routing defaults off, and secret-scanned or excluded prompts are withheld.
- The outbound service host is fixed as api.typesafe.ai, and redirects are refused.
- When routing is enabled with all required gates, prompt text may be sent to api.typesafe.ai for model classification.
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.430.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.430.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.