create-pmos@0.435.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 use authorizes a request to GitHub’s own release API, and the prompt-routing feature requires a user command and is restricted to the local workspace endpoint. The inspected CLI behavior matches the package’s scaffolding and optional workspace purpose.
Decision evidence
public snapshot- The package is a CLI scaffolder; its documented workspace activation is an explicit subcommand.
- The cockpit mod offer is additive and requires the user to trust the project; the CLI does not install it silently.
- Prompt routing requires the user to turn it on with a typed command.
- The routing endpoint accepts only the PMOS workspace’s loopback address.
- The optional Windows Git installer sends GITHUB_TOKEN to GitHub’s own release API.
- No malicious behavior was identified in the inspected source.
- The scanner’s credential-flow lead uses the token only with api.github.com.
- Routing forwards prompt and repository-root data only through an explicitly enabled local workspace route.
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.435.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.435.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.