create-pmos@0.480.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 process execution and configuration writes are part of the explicitly invoked scaffolding and workspace setup. Prompt routing is constrained to the local workspace and sends prompts externally only when its consent and configuration gates are enabled.
Decision evidence
public snapshot- The manifest exposes a command-line entry point and declares no lifecycle scripts.
- The cockpit hook accepts only the loopback URL supplied by the workspace.
- Prompt classification requires a key, repository consent, and routing enabled; secret-scanned or excluded prompts are withheld.
- The external classification service host is fixed as api.typesafe.ai.
- When routing is configured and consented to, qualifying prompts may be sent to api.typesafe.ai for model 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.480.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.480.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.