create-pmos@0.479.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 flagged credential and network behavior belongs to the workspace’s documented prompt-routing feature, which sends prompts only after explicit consent and opt-in. The package’s entry point is an explicitly invoked CLI, with no install lifecycle scripts identified.
Decision evidence
public snapshot- The package exposes its scaffolding and workspace behavior through an explicit CLI; no install lifecycle scripts were found.
- Prompt routing requires a saved key, repository consent, and a separate routing switch that is off by default.
- The router withholds prompts matching its secret scan or excluded paths before sending them.
- The outbound service is the fixed TypeSafe endpoint, and documentation explains what prompt text is sent and how to disable routing.
- When all routing gates are enabled, typed prompts may be sent to api.typesafe.ai for classification.
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.479.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.479.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.