Repo brief: Col-E/Recaf

Generated by RepoPilot · document generated 2026-09-14 · concise human review Evidence snapshot · analyzed 2026-09-14T07:53:43.493Z · commit 34802966f991

Verdict

Mixed — Single-maintainer risk — review before adopting

• Last commit 1w ago
• 4 active contributors
• MIT licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

Recaf is a modern Java bytecode editor that lets users visually edit compiled Java classes without manually managing the constant pool, stack frames, or instruction selection. It abstracts away the complexity of bytecode manipulation while supporting both standard Java and Android applications, and includes integrated decompilers, a bytecode assembler, a built-in compiler, and deobfuscation tools. Multi-module Gradle project: recaf-core is the main library module under recaf-core/src/main/java/software/coley/recaf/, organized by feature domains (analytics, cdi, behavior, logging). Bootstrap.java is the entry point. CDI (Contexts and Dependency Injection via Jakarta) handles initialization…

Start here

Open these first:

• recaf-core/src/main/java/software/coley/recaf/Recaf.java — Main entry point for the Recaf application; all contributors must understand the application lifecycle and initialization…
• recaf-core/src/main/java/software/coley/recaf/Bootstrap.java — Bootstrap initialization sequence that sets up CDI, logging, and system resources before Recaf starts
• recaf-core/src/main/java/software/coley/recaf/info/ClassInfo.java — Core abstraction for Java class metadata; fundamental to bytecode editing operations throughout the codebase
• recaf-core/src/main/java/software/coley/recaf/cdi/EagerInitializationExtension.java — CDI extension managing dependency injection and bean lifecycle; essential for understanding how services are wired
• recaf-core/src/main/java/software/coley/recaf/config/ConfigPersistence.java — Configuration persistence layer that manages user settings and state; critical for data durability

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.

Check README for instructions.

Daily commands:

./gradlew build

For UI: use the Launcher (separate repo) or snapshot artifacts. The core library can be consumed as a dependency; running the full editor requires the UI module (not shown in file list, likely in a separate module or br…

…shortened for this brief.

Key cautions & unknowns

• Small team — 4 contributors active in recent commits
• Single-maintainer risk — top contributor 93% of recent commits
• 1. No UI module in provided file list: The UI is likely in a separate submodule or branch not shown; just building recaf-core produces a library, not a runnable editor. 2. Snapshot-only builds: v4.0.0-SNAPSHOT…
• 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.