create-pmos@0.424.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’s main behavior is a user-invoked scaffolder, with no install lifecycle scripts. Flagged credential and network behavior is limited to GitHub’s API for Portable Git setup and consent-gated prompt routing through a loopback workspace service.
Decision evidence
public snapshot- The manifest exposes a CLI entry point; no install lifecycle scripts are declared.
- The workspace subcommand is documented as opt-in and installs its native dependency only when explicitly requested.
- Prompt routing accepts only a loopback workspace URL.
- Routing prompts to Jev requires a valid saved key, repository consent, and routing enabled; the implementation withholds prompts that match its secret scan or excluded paths.
- The Windows setup script sends an optional GitHub token to GitHub’s API to retrieve Portable Git release metadata.
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.424.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.424.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.