create-pmos@0.423.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-aiNo malicious credential exfiltration or install-time attack was established. However, the scaffolding command enables a plugin by writing repository-level Claude Code settings, which is a meaningful agent capability change and merits a warning.
Decision evidence
public snapshot- The scaffolder offers the cockpit mod through repository Claude settings unless the user passes --no-mod.
- The offered settings enable pmos-cockpit and register the local ./pmos/mods marketplace.
- The mod settings are written to the repository's .claude/settings.json.
- Prompt routing reads PMOS_ROUTE_URL from the environment and sends prompts only when that URL is configured.
- The package exposes a user-run scaffolding command; the mod offer can be skipped with --no-mod.
- The routing hook does nothing when PMOS_ROUTE_URL is unset, and uses that configured URL when sending prompts.
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.423.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.423.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.