create-pmos@0.467.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 5d ago · by lpm-firewall-aiThe flagged credential and network behavior is part of the package’s model-routing feature: prompts go through a local workspace and leave the machine only after consent and routing are enabled. The package uses an explicit CLI and has no lifecycle scripts in the inspected manifest.
Decision evidence
public snapshot- The package exposes an explicit `create-pmos` CLI for scaffolding; the cockpit mod is offered through the repository settings when that command is run.
- Prompt routing sends requests to the workspace loopback address; the workspace requires a saved key, repository consent, and routing enabled before sending prompts to Jev, and filters secrets and excluded paths.
- The inspected package manifest declares no lifecycle scripts.
- The cockpit routing path is gated by user consent and an explicit setting that defaults off; the mod does not receive the Jev key.
Source & flagged code
11 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.467.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.467.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.