Security fixes are applied to the latest released version of cmdpeek.

Please do not report security vulnerabilities through public GitHub issues.

Use GitHub's private vulnerability reporting feature for this repository when available.

Include:

• a clear description of the issue
• affected versions
• steps to reproduce
• potential impact
• any suggested mitigation

Please avoid including credentials, access tokens, private configuration files, infrastructure details or other sensitive data.

cmdpeek executes local shell commands with the current user's environment and permissions.

A configuration may:

• read or modify files;
• start processes;
• access the network;
• invoke credentials available to the user;
• run destructive commands.

Do not use untrusted configuration files.

Variable values are currently inserted directly into command templates.

Example:

run: git commit -m "{{message}}"

The surrounding quotes help with ordinary spaces, but they do not provide general shell-safe escaping for arbitrary input.

Review the final rendered command before confirming execution.

A command variable runs its source command while resolving options.

source:
  type: command
  command: kubectl get namespaces

This happens before the final command confirmation. Treat command sources as executable code as well.

Values may be visible in:

• the live command preview;
• the final confirmation screen;
• terminal scrollback;
• recordings and screenshots;
• process arguments;
• command output.

Avoid placing secrets directly in variables when possible. Prefer environment variables or credential-aware tools.

Use clear titles, descriptions and labels:

title: Delete Kubernetes deployment
labels:
  - kubernetes
  - delete
  - destructive

Keep destructive operations separate from read-only workflows and make their effect obvious in the preview.