create-pmos@0.431.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 is an explicitly invoked scaffolder with no identified malicious behavior. The flagged credential is sent to GitHub's own releases API, and prompt routing is gated by saved credentials, repository consent, and an enabled setting.
Decision evidence
public snapshot- The package is a PMOS scaffolding CLI; its entry point dispatches behavior from command-line arguments.
- The CLI offers the cockpit plugin through project Claude settings, and the source says Claude Code asks the user to trust the project.
- The cockpit hook sends prompts to a loopback workspace URL; it does not receive the TypeSafe key.
- Prompt routing requires a saved key, repository consent, and routing enabled.
- The reviewed outbound classifier endpoint is fixed at api.typesafe.ai.
- The Windows installer uses GITHUB_TOKEN only as a Bearer credential for GitHub's own 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.431.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.431.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.