Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-375GitHub issuePublicDecided· Out of scope

monokai-pro.nvim theme fails to install: wrong GitHub owner (gthelding -> loctvl842)

Reported by yash-p-amd · filed Sep 18, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

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

monokai-pro.nvim theme fails to install: wrong GitHub owner (gthelding -> loctvl842)revision 1 · captured 2026-09-28 21:23 UTC via poll

What happened

Running nvim (fresh Lazy plugin install) fails to clone the monokai-pro.nvim theme:

monokai-pro.nvim
	Cloning into '/home/montu/.local/share/nvim/lazy/monokai-pro.nvim'...
remote: Repository not found.
fatal: repository 'https://github.com/gthelding/monokai-pro.nvim.git/' not found

Cause

The shipped omarchy-nvim theme list references the wrong GitHub owner for this plugin:

config/lua/plugins/all-themes.lua (as installed at /usr/share/omarchy-nvim/config/lua/plugins/all-themes.lua) has:

{
	"gthelding/monokai-pro.nvim",
	lazy = true,
	priority = 1000,
},

gthelding/monokai-pro.nvim does not exist on GitHub. The actual maintained repo is loctvl842/monokai-pro.nvim (verified reachable via git ls-remote).

Expected

The plugin spec should point at loctvl842/monokai-pro.nvim so Lazy can clone it successfully.

Steps to reproduce

  1. Fresh Omarchy install with omarchy-nvim package.
  2. Run nvim and let Lazy sync/install plugins.
  3. Observe the clone failure for monokai-pro.nvim.

System details

  • Omarchy version: 4.0.4-mac.1
  • omarchy-nvim package version: 2026.8.1-1

Suggested fix

Change the plugin source in all-themes.lua (and any related monokai-pro theme spec files) from:

"gthelding/monokai-pro.nvim"

to:

"loctvl842/monokai-pro.nvim"
View raw text
## What happened

Running `nvim` (fresh Lazy plugin install) fails to clone the `monokai-pro.nvim` theme:

```
monokai-pro.nvim
	Cloning into '/home/montu/.local/share/nvim/lazy/monokai-pro.nvim'...
remote: Repository not found.
fatal: repository 'https://github.com/gthelding/monokai-pro.nvim.git/' not found
```

## Cause

The shipped `omarchy-nvim` theme list references the wrong GitHub owner for this plugin:

`config/lua/plugins/all-themes.lua` (as installed at `/usr/share/omarchy-nvim/config/lua/plugins/all-themes.lua`) has:

```lua
{
	"gthelding/monokai-pro.nvim",
	lazy = true,
	priority = 1000,
},
```

`gthelding/monokai-pro.nvim` does not exist on GitHub. The actual maintained repo is `loctvl842/monokai-pro.nvim` (verified reachable via `git ls-remote`).

## Expected

The plugin spec should point at `loctvl842/monokai-pro.nvim` so Lazy can clone it successfully.

## Steps to reproduce

1. Fresh Omarchy install with `omarchy-nvim` package.
2. Run `nvim` and let Lazy sync/install plugins.
3. Observe the clone failure for `monokai-pro.nvim`.

## System details

- Omarchy version: 4.0.4-mac.1
- omarchy-nvim package version: 2026.8.1-1

## Suggested fix

Change the plugin source in `all-themes.lua` (and any related monokai-pro theme spec files) from:
```
"gthelding/monokai-pro.nvim"
```
to:
```
"loctvl842/monokai-pro.nvim"
```

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 15:14 UTC