Richard Ben Aleya

Richard Ben Aleya

Corpus Hub contributor since 2026-10-05

Richard Ben Aleya's work was selected for the XERJ Corpus Hub, the open reference memory AI coding agents search before they write code. When an agent meets the same problem, it gets this implementation back as a worked example, with the author and the repository attached.

2corpora
2selected commits
8files
156lines
★ 94GitHub stars on repo

Totals across every corpus @rbenaley appears in; a commit selected for two corpora counts once. Files and lines count the selected commits; each corpus indexes the whole repository at its pinned commit.

Selected work

GitHub ★ 94

rbenaley/Vauban

848b088d29 test(just): shorten validate and keep parallel tests stable
selected commit: 8 files · 156 lines · Rust, shell · shared, the project root, vauban-proxy-rdp

The corpus is the whole repository at the pinned commit, not only the files of the selected commit.

selected · in licence reviewcorpus rbenaley--vaubanSECBSD-2-Clausebastionrustsecurityprivileged-access-managementiacsindustrial agreed 2026-10-19

Not installable yet: this corpus is not in the hub registry until its licence review passes, so xerj corpus add and xerj ask cannot fetch it. It becomes installable when this card says live in the hub.

rbenaley/Vauban

c06d6f16db fix(mcp): harden hop 2 and close the review gaps (0.9.46)

The corpus is the whole repository at the pinned commit, not only the files of the selected commit.

selected · in licence reviewcorpus security-practiceBSD-2-Clause agreed 2026-10-05

Not installable yet: this corpus is not in the hub registry until its licence review passes, so xerj corpus add and xerj ask cannot fetch it. It becomes installable when this card says live in the hub.

XERJ Corpus Hub contributor badge
[![XERJ Corpus Hub contributor](https://hub.xerj.org/contributors/rbenaley/badge.svg)](https://hub.xerj.org/contributors/rbenaley)

Included with the author's permission (email, 2026-10-05), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.