create-pmos@0.405.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 12d ago · by lpm-firewall-aiThe flagged credential pattern is test data used to confirm secret-file rejection, and the plugin routing request is restricted to the workspace’s loopback endpoint. Agent configuration is project-scoped setup performed by the explicitly invoked CLI, which preserves existing settings; the inspected source establishes no concrete attack behavior.
Decision evidence
public snapshot- The package exposes a CLI entry point; no install lifecycle command appears in the inspected manifest.
- The CLI scaffolds a project when invoked and can add the package’s local cockpit plugin to that project’s Claude settings, preserving existing values.
- A workspace self-test creates a synthetic credential-like value and verifies that the share endpoint refuses the file.
- The plugin sends prompt-routing requests only to a loopback URL supplied by the workspace; its request includes the project root and prompt.
- The other inspected paths contain PMOS workflow scripts, workspace features, UI modules, and test fixtures; their excerpts did not establish an independent 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.405.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.405.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.