create-pmos@0.488.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 process, network, and configuration behaviors fit the package’s scaffolding and optional workspace features. Prompt routing requires a configured workspace endpoint and explicit user activation, and the inspected Anthropic key flow is confined to the API runner.
Decision evidence
public snapshot- The package identifies itself as a PMOS scaffolder and exposes a CLI entry point.
- The CLI selects an operation from the arguments the user invokes; the default operation vendors the bundled kit.
- Cockpit prompt routing uses the workspace-provided PMOS_ROUTE_URL.
- Routing can be enabled only by a person’s typed pmos-route command.
- The Anthropic key is used by the API runner and removed from the environment passed to its tool subprocesses.
- The cockpit can forward prompts for routing, but this requires a configured workspace URL and enabled routing.
- The CLI and installer include process execution and downloads for the explicitly requested workspace setup.
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.488.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.488.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.