[probonopd]

Repository: https://github.com/Opfour/op4

op4 is a terminal-based encrypted messaging application written in Rust. It provides end-to-end encrypted private messaging with post-quantum cryptography, routed entirely through the Tor anonymity network so that neither the content of your messages nor your IP address is exposed to anyone — not

• Stars: 6
• Release with the AppImage: v0.2.0-dev.2 (2026-03-24T02:58:20Z)
• AppImage asset: op4-0.2.0-dev.2-x86_64.AppImage
• License: AGPL-3.0

Found by .github/workflows/discover-apps.yml, which looks for GitHub
repositories that publish AppImages but are not in the catalog yet. This
entry was not tested by a human; please review it before merging.

[github-actions]

✅ Test passed

@Opfour: this pull request adds the AppImage from your GitHub repository to the AppImage catalog; the test reports the following. Could you have a look?

Please check that the screenshot shows the application's main window.

op4

Compatibility: not self-contained: uses the C library of the system; references glibc 2.34

Warnings:

• The screenshot may show an error message; please check it.
• The AppImage contains no update information, so users cannot update it with AppImageUpdate or similar tools. Please consider embedding it when building the AppImage (e.g., appimagetool -u) and publishing the .zsync file next to the AppImage; see https://docs.appimage.org/packaging-guide/optional/updates.html

Commit 1553f29. Full log

[Opfour]

Reviewed, thanks for picking this up.

• Screenshot: this is the intended first-run prompt. op4 is a terminal app, and on first launch it asks the user to set a vault passphrase. The [warn] mlockall failed (errno 12) line is expected inside a container, where the memlock limit is low. op4 keeps running, as the message itself says.
• Self-contained / update information: both are fixed in v0.3.2. The AppImage is now a static musl build with no glibc dependency. It embeds gh-releases-zsync|Opfour|op4|latest|op4-*-x86_64.AppImage.zsync, and the .zsync file is published with the release.

Could the test be re-run against v0.3.2?

[github-actions]

✅ Test passed

Please check that the screenshot shows the application's main window.

op4

Tested:

• op4-0.3.2-x86_64.AppImage from release v0.3.2

Compatibility: self-contained (contains no dynamically linked code)

Names:

WARNING: The names of the repository, the AppImage and the README differ: repository 'op4', AppImage 'op4', README 'Table of Contents'

Warnings:

• The repository, the AppImage and the README (whichever exist) call the application by different names (see the remarks below). Please check that they all belong to the same application, and that the name of the file in data/ is the right one.
• The screenshot may show an error message; please check it.

Commit 1553f29. Full log

[Opfour]

Hi maintainers — this is my project (Opfour/op4), the entry is accurate and the AppImage now ships with update information (.zsync) and a checksum in the latest release (v0.3.2). The catalog should pick up the latest release automatically from the repo. Could this be merged? Thanks!

[github-actions]

✅ Test passed

Please check that the screenshot shows the application's main window.

op4

Tested:

• op4-0.3.2-x86_64.AppImage from release v0.3.2

Compatibility: self-contained (contains no dynamically linked code)

Names:

WARNING: The names of the repository, the AppImage and the README differ: repository 'op4', AppImage 'op4', README 'Table of Contents'

Warnings:

• The repository, the AppImage and the README (whichever exist) call the application by different names (see the remarks below). Please check that they all belong to the same application, and that the name of the file in data/ is the right one.
• The screenshot may show an error message; please check it.

Commit 1553f29. Full log