create-pmos@0.433.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 routed credential flows lead to the local workspace and, when configured, the service associated with the user’s TypeSafe key. The installer’s GitHub token is sent to api.github.com for Git release metadata; the inspected behavior does not show exfiltration or unauthorized actions.
Decision evidence
public snapshot- The manifest describes a PMOS scaffolding CLI and exposes bin/create-pmos.js.
- The CLI copies the bundled kit into the target repository when the user runs its vendor command.
- The cockpit hook sends prompts only to the workspace-provided loopback URL; it sends nothing when that URL is absent.
- Prompt classification requires a saved key, repository consent, and routing enabled; rules and secret scanning can withhold prompts.
- The workspace’s hosted classifier uses api.typesafe.ai, the service corresponding to the user-supplied TypeSafe key.
- The PowerShell installer uses GITHUB_TOKEN only for the GitHub API request to find Portable Git releases.
- The scanner flagged credential transport and agent configuration writes, but the inspected flows use an authenticated service endpoint or project-local setup invoked by the CLI.
- The installer runs commands and downloads tools, but the inspected downloads are for the package’s documented setup components.
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.433.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.433.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.