create-pmos@0.427.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 flows are bounded to GitHub’s release API and an opt-in TypeSafe classifier at a fixed host. The cockpit hook itself only contacts a loopback workspace endpoint, and prompt routing is disabled by default.
Decision evidence
public snapshot- The manifest exposes `bin/create-pmos.js` as the package CLI.
- The workspace install and launch path is a distinct `workspace` command.
- Prompt routing requires a key, repository consent, and a route switch; the route switch defaults off.
- The remote classifier uses the fixed `api.typesafe.ai/v1/systemone` endpoint and refuses redirects.
- The cockpit hook sends prompts only to the workspace’s loopback URL; without that URL, it asks no host.
- `GITHUB_TOKEN`, when present, is sent to GitHub’s Git-for-Windows release API request.
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.427.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.427.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.