create-pmos@0.530.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 8h ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, and the CLI’s filesystem and agent-configuration changes occur when the user invokes its scaffolding command. The flagged routing code sends prompts only to a PMOS workspace loopback endpoint, with no evidence of credential theft or unrelated outbound collection.
Decision evidence
public snapshot- The executable performs scaffolding only when invoked as the CLI.
- The cockpit settings entry offers a bundled mod from ./pmos/mods.
- Prompt routing sends requests to a PMOS workspace loopback endpoint; the mod does not receive the Jev key.
- Routing accepts only a loopback URL, and sub-agent prompts are routed only when routing is enabled and no model was specified.
Source & flagged code
25 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 · L23Findings
Affected versions and remediation
This report applies to create-pmos@0.530.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.530.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.