create-pmos@0.466.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 resolves to a user-run installer and a prompt-routing feature whose external send requires a saved key, repository consent, and a route switch that defaults off. The inspected source does not show malicious credential collection or unauthorized account actions.
Decision evidence
public snapshot- The manifest exposes a `create-pmos` CLI; no npm lifecycle script is present.
- The CLI adds a local cockpit plugin entry to the repository’s Claude settings as part of scaffolding.
- The hook routes eligible prompts through a loopback workspace endpoint, and routing to Jev requires a saved key, repository consent, and a route switch that defaults off.
- The workspace route code withholds prompts that match its secret scan or excluded paths.
- The cockpit hook can send prompt text and the repository root to the local workspace route endpoint when routing is active.
- The CLI enables a project-local Claude plugin entry during scaffolding.
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.466.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.466.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.