create-pmos@0.484.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 3d ago · by lpm-firewall-aiThe flagged credential and network behavior resolves to prompt routing through the PMOS workspace’s loopback endpoint, with separate consent and routing gates before prompts can reach Jev. The CLI’s project-level plugin setup matches the package’s scaffolding purpose.
Decision evidence
public snapshot- The package describes a local PMOS kit scaffold and exposes a CLI entry point.
- The scaffold copies its bundled payload into the target repository when the CLI is run.
- The cockpit offers its project plugin through a specific project settings file.
- The routing hook uses the PMOS_ROUTE_URL value and proceeds only when a URL is available.
- The routing URL is restricted to a loopback address supplied by the workspace.
- Sending prompts to Jev requires a saved key, repository consent, and a routing switch that defaults off.
- The router skips Jev when a rule decides first, and scans prompts for secrets before sending.
Source & flagged code
14 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.484.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.484.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.