create-pmos@0.443.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 inspected network flows support the package's setup and model-routing features: GitHub credentials are used for GitHub release metadata, while prompt forwarding to Jev requires repository consent and a default-off switch. No malicious behavior was identified in the flagged paths.
Decision evidence
public snapshot- The package is a PMOS workflow and local workspace scaffold intended to operate in the user's repository.
- Prompt routing sends text to Jev only when a saved key, repository consent, and the default-off routing switch are all present; prompts that fail the secret scan are withheld.
- The cockpit sends the repository root and prompt to its configured route URL; the workspace sets that URL to loopback and keeps the Jev key there.
- The Windows setup script uses GITHUB_TOKEN only for GitHub's Git for Windows release metadata 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.443.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.443.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.