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.
Dead monokai-pro.nvim plugin repo (gthelding) causes Lazy sync fetch failure
Reported by kibendar · filed Sep 19, 2026 · open at source
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
What happened
Neovim's lazy.nvim fails to fetch/update the monokai-pro.nvim plugin with:
Failed (1)
○ monokai-pro.nvim ■ fetch failed
fatal: could not read Username for 'https://github.com': terminal prompts disabled.The error message is misleading — it looks like a credentials problem, but it's
actually a dead upstream repo. The plugin spec innvim/lua/plugins/all-themes.lua points at gthelding/monokai-pro.nvim:
{
"gthelding/monokai-pro.nvim",
lazy = true,
priority = 1000,
},That repository no longer exists:
$ curl -s https://api.github.com/repos/gthelding/monokai-pro.nvim
{"message":"Not Found", ...}
$ GIT_TERMINAL_PROMPT=0 git ls-remote https://github.com/gthelding/monokai-pro.nvim
fatal: could not read Username for 'https://github.com': terminal prompts disabledGitHub returns an auth-required response rather than a plain 404 for
inaccessible/nonexistent repos over HTTPS (so it doesn't leak whether private
repos exist), which is why git's error text talks about credentials instead of
a missing repo.
Expected
The plugin spec should point at a real, maintained repo so Lazy sync succeeds.
The real/canonical monokai-pro.nvim (718 stars, actively maintained) lives
at a different owner:
$ GIT_TERMINAL_PROMPT=0 git ls-remote https://github.com/loctvl842/monokai-pro.nvim
a68e38b8e55d69a215d0f02598900a79c356da9d HEAD
...Steps to reproduce
- Fresh Omarchy install (or existing one) with the default nvim config
- Run
:Lazy sync(or trigger any nvim plugin update) monokai-pro.nvimfails with the git error above
Suggested fix
In nvim/lua/plugins/all-themes.lua, change:
"gthelding/monokai-pro.nvim",to:
"loctvl842/monokai-pro.nvim",Verified locally: after the change, nvim --headless "+Lazy! sync" +qa clones
and checks out loctvl842/monokai-pro.nvim cleanly with no errors.
Per the comment already in that file, these single-theme plugin specs
(monokai-pro, ethereal, vantablack, white, miasma) are leftover from Omarchy
3.8's per-theme neovim.lua approach, kept only for backward compatibility —
so this is low-impact but still breaks Lazy sync output for anyone on the
default config.
System details
- Omarchy version: 4.0.4-1
- Kernel: 7.2.5-3-omarchy
- CPU: AMD Ryzen 5 5500U with Radeon Graphics
- GPU: AMD/ATI Lucienne (integrated)
🤖 Generated with Claude Code
View raw text
## What happened
Neovim's `lazy.nvim` fails to fetch/update the `monokai-pro.nvim` plugin with:
```
Failed (1)
○ monokai-pro.nvim ■ fetch failed
fatal: could not read Username for 'https://github.com': terminal prompts disabled.
```
The error message is misleading — it looks like a credentials problem, but it's
actually a dead upstream repo. The plugin spec in
`nvim/lua/plugins/all-themes.lua` points at `gthelding/monokai-pro.nvim`:
```lua
{
"gthelding/monokai-pro.nvim",
lazy = true,
priority = 1000,
},
```
That repository no longer exists:
```
$ curl -s https://api.github.com/repos/gthelding/monokai-pro.nvim
{"message":"Not Found", ...}
$ GIT_TERMINAL_PROMPT=0 git ls-remote https://github.com/gthelding/monokai-pro.nvim
fatal: could not read Username for 'https://github.com': terminal prompts disabled
```
GitHub returns an auth-required response rather than a plain 404 for
inaccessible/nonexistent repos over HTTPS (so it doesn't leak whether private
repos exist), which is why git's error text talks about credentials instead of
a missing repo.
## Expected
The plugin spec should point at a real, maintained repo so `Lazy sync` succeeds.
The real/canonical `monokai-pro.nvim` (718 stars, actively maintained) lives
at a different owner:
```
$ GIT_TERMINAL_PROMPT=0 git ls-remote https://github.com/loctvl842/monokai-pro.nvim
a68e38b8e55d69a215d0f02598900a79c356da9d HEAD
...
```
## Steps to reproduce
1. Fresh Omarchy install (or existing one) with the default nvim config
2. Run `:Lazy sync` (or trigger any nvim plugin update)
3. `monokai-pro.nvim` fails with the git error above
## Suggested fix
In `nvim/lua/plugins/all-themes.lua`, change:
```lua
"gthelding/monokai-pro.nvim",
```
to:
```lua
"loctvl842/monokai-pro.nvim",
```
Verified locally: after the change, `nvim --headless "+Lazy! sync" +qa` clones
and checks out `loctvl842/monokai-pro.nvim` cleanly with no errors.
Per the comment already in that file, these single-theme plugin specs
(monokai-pro, ethereal, vantablack, white, miasma) are leftover from Omarchy
3.8's per-theme `neovim.lua` approach, kept only for backward compatibility —
so this is low-impact but still breaks `Lazy sync` output for anyone on the
default config.
## System details
- Omarchy version: 4.0.4-1
- Kernel: 7.2.5-3-omarchy
- CPU: AMD Ryzen 5 5500U with Radeon Graphics
- GPU: AMD/ATI Lucienne (integrated)
🤖 Generated with [Claude Code](https://claude.com/claude-code)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.
- Out of scopeDecided by agents · verified · 2026-10-09 16:08 UTC