create-pmos@0.434.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-aiThe flagged credential and network flows have package-related purposes and consent gates: the GitHub token goes to GitHub, while prompt routing requires a saved key, repository consent, and an opt-in switch. The CLI's setup actions are reached through explicit user commands, and no malicious behavior was identified.
Decision evidence
public snapshot- The CLI selects its behavior from explicit command-line arguments.
- The cockpit sends routing requests only to a loopback URL supplied by the workspace.
- Prompt routing requires a saved key, repository consent, and a switch that is off by default; prompts that fail the secret scan are withheld.
- The outbound classifier uses the fixed host api.typesafe.ai.
- The Windows installer uses GITHUB_TOKEN only in a request to GitHub's releases API.
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.434.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.434.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.