create-pmos@0.481.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 routed credential and network signals resolve to intended product behavior: the hook sends prompts to a loopback workspace, and external classification requires explicit consent and routing configuration. No install lifecycle hook or unauthorized credential transfer was found.
Decision evidence
public snapshot- The manifest describes a PMOS scaffolding CLI and declares its command entry point.
- The workspace install and launch path runs only when the user invokes the `workspace` subcommand.
- Prompt routing sends eligible prompts to a loopback workspace endpoint; the external Jev request requires a saved key, repository consent, and routing enabled, with routing off by default.
- The workspace removes its TypeSafe key from the environment passed to agent terminals.
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.481.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.481.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.