create-pmos@0.436.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 package has no install lifecycle scripts, and the flagged credential flow sends a GitHub token only to GitHub for release metadata. Its prompt-routing feature is documented and requires consent, a saved key, and an off-by-default switch.
Decision evidence
public snapshot- The package exposes a CLI entry point; no lifecycle scripts were found.
- The CLI selects vendoring, updating, or workspace activation from explicit command arguments.
- The Claude Code marketplace and enabled plugin point to the package’s own local PMOS mod.
- The Windows installer sends GITHUB_TOKEN to GitHub’s API to read Git for Windows release metadata.
- Prompt routing requires a saved key, repository consent, and a route switch that defaults off; the guide explains what is sent.
- The Windows installer can send a GitHub token, but only to api.github.com for release metadata.
- The workspace can route prompts to TypeSafe, but routing is disclosed and requires explicit consent and an enabled switch.
- The CLI can write project files and Claude settings as part of the user-invoked scaffolding command.
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.436.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.436.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.