Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
1Password clipboard history
Reported by ghost · filed Jul 10, 2025Closed upstream on 2025-07-10 by dhh; the closing comment says it was fixed by PR #113. GitHub close reason: completed.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
With wl-paste -l, you can see the mime type of the current value on the clipboard.
When copying normal text, it looks like this:
text/plain;charset=utf-8
UTF8_STRING
STRING
TEXT
text/plainWhen I copy a password from KeePassXC, it looks like this:
text/plain
x-kde-passwordManagerHint
text/plain;charset=utf-8When I copy a password from 1Password, I get the first version.
It would be great if we could convince 1Password to also set that additional mime type.
wl-clipboard also made an unreleased change to set the CLIPBOARD_STATE env variable to sensitive if that mime type is used. If that is released, clipse, cliphist, ... can use that env variable to skip the current clipboard value.
There is already an issue to ask for a new release of wl-clipboard, and there is an issue to make a change to Clipse.
wl-clip-hist also has the option to filter on mime type. From the FAQ:wl-clip-persist --clipboard regular --all-mime-type-regex '^(?!x-kde-passwordManagerHint).+'
View raw text
With `wl-paste -l`, you can see the mime type of the current value on the clipboard. When copying normal text, it looks like this: ``` text/plain;charset=utf-8 UTF8_STRING STRING TEXT text/plain ``` When I copy a password from KeePassXC, it looks like this: ``` text/plain x-kde-passwordManagerHint text/plain;charset=utf-8 ``` When I copy a password from 1Password, I get the first version. It would be great if we could convince 1Password to also set that additional mime type. `wl-clipboard` also made an unreleased [change](https://github.com/bugaevc/wl-clipboard/commit/1e50b65d5ef94d2e595cfaf30a81f933ba80b1f9) to set the CLIPBOARD_STATE env variable to sensitive if that mime type is used. If that is released, clipse, cliphist, ... can use that env variable to skip the current clipboard value. There is already an [issue](https://github.com/bugaevc/wl-clipboard/issues/260) to ask for a new release of wl-clipboard, and there is an [issue](https://github.com/savedra1/clipse/issues/222) to make a change to Clipse. `wl-clip-hist` also has the option to filter on mime type. From the [FAQ](https://github.com/Linus789/wl-clip-persist?tab=readme-ov-file#is-it-possible-to-ignore-clipboard-events-from-password-managers): `wl-clip-persist --clipboard regular --all-mime-type-regex '^(?!x-kde-passwordManagerHint).+'`
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.