create-pmos@0.518.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 22h ago · by lpm-firewall-aiThe package exposes a scaffolding CLI without lifecycle scripts. Its agent setup is limited to its own plugin and skills when the user runs the CLI, and external prompt routing requires a saved key, repository consent, and an enabled setting.
Decision evidence
public snapshot- The package is a PMOS scaffolder with a CLI entry point; no npm lifecycle scripts are declared.
- Project setup and workspace activation run through explicit CLI subcommands.
- The cockpit setup adds this package’s own plugin and skill links to the target repository.
- Prompt routing requires a saved key, repository consent, and routing enabled; routing is off by default.
- Prompts containing detected secrets or excluded paths are withheld from routing.
- The external classifier uses the fixed host api.typesafe.ai; the cockpit reaches it through the workspace’s loopback endpoint and does not receive its key.
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 · L23Package source references shell execution.
bin/create-pmos.jsFindings
Affected versions and remediation
This report applies to create-pmos@0.518.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.518.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.