create-pmos@0.416.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 10d ago · by lpm-firewall-aiThe explicitly invoked scaffolder performs first-party agent configuration that can enable a plugin for later sessions, leaving a guarded agent capability risk. Inspected credential-related test code verifies rejection of a file containing a sample secret.
Decision evidence
public snapshot- Running the scaffolder calls the mod setup unless the user passes --no-mod.
- The setup adds the package’s first-party cockpit plugin to the repository’s Claude settings and enables it when that key is absent.
- The plugin is described as checking PMOS skills and guarding merge actions and ledgers.
- The share test writes a sample secret and verifies the share endpoint refuses the file.
- The tool.check hook proceeds only after the host allows a call, then classifies it using the event’s tool and input.
- The file viewer fetches JSON and text using same-origin credentials.
- classifyTool examines the event’s tool name and recognizes MCP merge operations.
- formatStatus receives repository and initiative status fields and cleans the repository value for display.
- The configuration change occurs through the explicitly invoked scaffolding command; the source also provides a --no-mod option.
- The inspected share test demonstrates secret-file rejection rather than credential transfer.
Source & flagged code
12 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.416.0.
See all versions of create-pmos for other recorded verdicts.
- Review the evidence and your use of create-pmos@0.416.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.