Javanshir

Javanshir

Corpus Hub contributor since 2026-10-29

Javanshir'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.

3corpora
1selected commit
22files
351lines
★ 11GitHub stars on repos

Totals across every corpus @Cavanshirpro 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 ★ 8

Cavanshirpro/curseforgepy

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

live on the hub · licence clearedcorpus cavanshirpro--curseforgepyAPIMIT agreed 2026-10-31
GitHub ★ 3

Cavanshirpro/discord.cpp-self

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

live on the hub · licence clearedcorpus cavanshirpro--discord-cpp-selfAPILGPL-3.0cmakeconancppcpp20discordvcpkg agreed 2026-10-31

Commit to YoungLionOrganization/YLSpec

060d431435 feat(jvm): add Java JNI API, Kotlin extensions, and Android AAR integ…
selected commit: 22 files · 351 lines · Java, Kotlin · jvm, javascript

The corpus covers only the directories this commit changed (javascript/test, jvm). The repository is @YoungLionOrganization's; this page credits @Cavanshirpro for this commit only.

live on the hub · licence clearedcorpus younglionorganization--ylspecWEBApache-2.0androidcjavakotlinmetadatanodejs agreed 2026-10-29
XERJ Corpus Hub contributor badge
[![XERJ Corpus Hub contributor](https://hub.xerj.org/contributors/Cavanshirpro/badge.svg)](https://hub.xerj.org/contributors/Cavanshirpro)

Included with the author's permission (email, 2026-10-29), under each repository's own licence, with attribution. Own more repositories? Sign in with GitHub and add them. Want something removed? Reply to the email, withdraw it on /add, or open an issue on xerj-org/xerj.