create-pmos@0.410.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 11d ago · by lpm-firewall-aiThe manifest exposes a user-run CLI without lifecycle hooks. The flagged settings mutation is an explicit scaffold feature for the package’s own mod, and the inspected network and test paths did not establish malicious behavior.
Decision evidence
public snapshot- The package exposes a user-run CLI, with no lifecycle hook shown in its manifest; the scaffold copies the bundled kit and offers the first-party cockpit mod through repository settings.
- The settings change is limited to offering the package’s own mod, preserves existing values, and can be skipped with --no-mod.
- Prompt routing uses a workspace-provided local endpoint and requires a saved key, repository consent, and an enabled routing setting.
- The flagged share-test code uses a synthetic secret that it verifies is refused; the other cited paths are bundled workflow, UI, guard, fixture, or test modules, and inspection found no separate confirmed attack.
Source & flagged code
11 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.410.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.410.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.