create-pmos@0.472.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 4d ago · by lpm-firewall-aiThe source shows an explicitly invoked project scaffold and optional workspace installer, with no lifecycle scripts. The flagged prompt transport is restricted to loopback and external classification is gated by the user’s saved key, consent, and routing setting; the GitHub token is sent to GitHub’s own API.
Decision evidence
public snapshot- The package has no lifecycle scripts; its executable dispatches explicit scaffold, update, version, and workspace commands.
- The scaffold copies the kit into the chosen repository and offers its cockpit mod through that repository’s settings.
- Prompt routing accepts only the workspace’s loopback URL; the workspace gates external classification on a saved key, consent, and routing being enabled.
- The guide says prompt routing is off until the user turns it on, and describes the conditions for sending typed prompts to Jev.
- The optional Windows installer uses GITHUB_TOKEN only in an Authorization header to api.github.com to look up the official Git for Windows release.
Source & flagged code
13 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.472.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.472.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.