create-pmos@0.470.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 source supports the package’s stated scaffolding and local workspace purpose. The flagged prompt-routing behavior is disclosed, defaults off at its consent gate, filters secrets and excluded paths, and keeps its service key out of agent environments.
Decision evidence
public snapshot- The manifest describes a PMOS scaffolding CLI, with `bin/create-pmos.js` as its command entry point.
- The workspace and native dependency setup are tied to the explicit `workspace` subcommand.
- Prompt routing requires a saved TypeSafe key, repository consent, and a routing switch that defaults off.
- Routing withholds prompts that match a secret scan or name an excluded path.
- The guide discloses that enabled routing sends typed prompts to Jev and explains the required consent and filtering.
- The workspace keeps the TypeSafe key out of agent environments and provides the mod only a loopback route URL.
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.470.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.470.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.