create-pmos@0.438.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 prompt transport is part of the package’s model-routing feature and is gated by a saved key, repository consent, and a switch that defaults off. The installer’s GitHub token use is directed to GitHub for a Portable Git release lookup; no malicious behavior was identified.
Decision evidence
public snapshot- The cockpit sends a prompt and repository root to its configured routing URL.
- The routing URL accepts only the workspace’s loopback address and route path.
- Prompt routing requires a saved key, repository consent, and a switch that defaults off.
- When enabled, classification uses the fixed api.typesafe.ai/v1/systemone endpoint.
- The CLI offers the bundled cockpit mod while setting up the kit in the repository.
- When prompt routing is enabled, prompt text may be sent to TypeSafe for classification.
- The Windows installer can send GITHUB_TOKEN to api.github.com to check for Portable Git releases.
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.438.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.438.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.