create-pmos@0.498.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 2d ago · by lpm-firewall-aiThe manifest exposes a CLI without lifecycle scripts, and the reviewed file writes and credential-helper setup occur through user-invoked commands. Prompt routing is limited to a workspace-provided loopback endpoint, with no evidence of unrelated credential collection or exfiltration.
Decision evidence
public snapshot- The package exposes a CLI entry point and declares no lifecycle scripts in its manifest.
- The CLI writes the kit and offers its local cockpit mod as part of the explicit scaffold command.
- The cockpit mod routes prompts only to a loopback address provided by the workspace; it sends nothing when that address is absent.
- The GitHub credential helper is configured for a repository only after the user supplies a GitHub login.
- The manifest describes the workspace GUI as a local companion app.
- The new Git identity feature stores repository-specific identity and login settings.
Source & flagged code
14 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.498.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.498.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.