create-pmos@0.524.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 8h ago · by lpm-firewall-aiThe flagged process execution and configuration writes implement the package's user-run scaffolding and workspace setup. Prompt routing's external service path requires a saved key, repository consent, and a switch that defaults off.
Decision evidence
public snapshot- The package provides a scaffold CLI, and the CLI runs its main actions only when invoked directly.
- The cockpit setup adds a project-local marketplace and plugin entry to .claude/settings.json.
- Prompt routing contacts only a loopback workspace endpoint; the mod does not receive the Jev key.
- Sending prompts to api.typesafe.ai requires a saved key, repository consent, and a separate switch that defaults off.
- The CLI and workspace use child processes and write project files, but these actions support the package's stated scaffolding and GUI features and are user-triggered.
Source & flagged code
25 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 · L23Findings
Affected versions and remediation
This report applies to create-pmos@0.524.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.524.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.