Repo brief: azahar-emu/azahar

Generated by RepoPilot · document generated 2026-09-13 · concise human review Evidence snapshot · analyzed 2026-09-13T19:29:02.556Z · commit 3392c56ce02b

Verdict

Healthy — Strong maintenance signals

• Last commit today
• 19 active contributors
• Distributed ownership (top contributor 34% of recent commits)
• GPL-2.0 licensed
• 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

Azahar is an open-source Nintendo 3DS emulator written primarily in C++ that emerged from merging PabloMK7's Citra fork and the Lime3DS project after Citra's shutdown. It emulates 3DS hardware across Windows, macOS, Android, and Linux, enabling users to play 3DS games with enhanced graphics, cheats, and netplay support. The project includes a full Android port (in Kotlin) alongside the native C++ core. Dual-architecture monorepo: src/CMakeLists.txt orchestrates the core C++ emulator engine; src/android/ contains a complete Kotlin/Gradle Android application (src/android/app/build.gradle.kts is the Android build manifest) with UI activities, adapters, dialogs, and feature modules (cheats,…

Start here

Open these first:

• src/android/app/build.gradle.kts — Build configuration for Android application; defines dependencies, SDK targets, and compilation settings that all…
• src/android/app/src/main/java/org/citra/citra_emu/NativeLibrary.kt — JNI bridge to native 3DS emulation core; critical integration point between Java UI and C++ emulator engine.
• src/android/app/src/main/java/org/citra/citra_emu/activities/EmulationActivity.kt — Main emulation window and game runtime activity; entry point for all game execution and input handling.
• src/android/app/src/main/java/org/citra/citra_emu/features/settings/model/Settings.kt — Central settings model managing emulator configuration across all features; touches cheats, display, audio, and input.
• src/CMakeLists.txt — Root CMake build configuration for native C++ emulation core compilation; required for all platform builds.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Verify the repository manifest and documentation before running setup commands—no package manager manifest (conanfile.txt, vcpkg.json, CMakeLists.txt root dependencies) is visible in the provided data. For Android build…

Daily commands:

Android: cd src/android && ./gradlew installDebug (requires Android SDK/NDK). Native (Linux/macOS/Windows): Verify CMake, C++ compiler (MSVC, GCC, or Clang), and dependencies in repository docs, then `mkdir bu…

…shortened for this brief.

Key cautions & unknowns

• GPL-2.0 is copyleft — check downstream compatibility
• Scorecard: default branch unprotected (0/10)
• Android NDK/SDK Path: build.gradle.kts likely requires ANDROID_SDK_ROOT and ANDROID_NDK_ROOT environment variables pointing to valid Android SDK/NDK installations—failure is silent if misconfigured. **Gradle…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.