Skip to content

Security: gsus67/omarchy-taskbar

Security

SECURITY.md

Security

Please report vulnerabilities privately through GitHub security advisories instead of a public issue.

Every change runs, in CI:

  • static QML checks: every text element renders plain text (window titles can come from any web page) and the QML references no remote URL;
  • guards for the commands it runs: every bash -c script is made of string literals only and receives window data as positional arguments, never pasted into the script; other programs start from argument lists, without a shell;
  • native Qt/Quickshell checks in a disposable CI container: launcher permission regressions, Crystal rendering, serialized settings writes and icon-scan debounce under a burst of events, including an idle check against polling;
  • ShellCheck on standalone scripts and each embedded bash -c script;
  • CodeQL security-extended analysis and zizmor for the workflows;
  • OpenSSF Scorecard (weekly and on main) for the repository's practices.

Generated launchers are stored under the plugin-owned ~/.local/share/applications/omarchy-taskbar/ directory with mode 0700. New launcher files use 0600; repair retains the existing file mode. Legacy migration removes group/other permissions and retains the owner's bits. The standard applications directory and other user-owned files are not chmodded. The original dropped launcher is not modified. Pinning does not execute it.

Appearance choices use fixed values and the existing atomic configuration writer, with serialized writes. Crystal is rendered locally; it does not activate the compositor's blur engine or add privileges, packages, background services, network requests or compositor configuration files.

There aren't any published security advisories