create-pmos@0.478.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 4d ago · by lpm-firewall-aiThe manifest exposes a user-invoked CLI without lifecycle scripts. The flagged prompt-routing hook reaches only a loopback workspace endpoint, and external routing requires a saved key, repository consent, and an opt-in switch that defaults off.
Decision evidence
public snapshot- The launcher runs as a user-invoked CLI and documents scaffolding and workspace commands.
- Prompt routing accepts only a loopback URL supplied through PMOS_ROUTE_URL.
- The workspace requires a saved key, repository consent, and routing enabled; routing defaults off.
- The launcher’s cockpit settings changes occur as part of an explicit scaffold command.
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.478.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.478.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.