Repo brief: objectbox/objectbox-java

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T15:03:04.926Z · commit e912fe328192

Verdict

Mixed — Single-maintainer risk — review before adopting

• Last commit 5w ago
• 3 active contributors
• Apache-2.0 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, cross-checked against OpenSSF Scorecard

What it is

ObjectBox Java is a lightweight, embedded on-device database for Android and JVM applications, optimized for fast CRUD operations and vector search. It provides an object-oriented API (via @Entity-annotated classes) to persist and query Java/Kotlin objects without SQL boilerplate, with built-in vector database capabilities for AI/RAG use cases. Gradle monorepo: objectbox-android/ contains Android-specific bindings and admin UI (split into adminIncluded/adminExcluded variants); build-logic/ defines shared Gradle conventions (dokka, publishing); root build.gradle.kts and gradle/libs.versions.toml centralize dependencies. CI split into main Jenkinsfile and Windows-specific variant in ci/.

Start here

Open these first:

• build.gradle.kts — Root build configuration defining project structure, dependency versions, and publication settings for all modules.
• gradle/libs.versions.toml — Centralized dependency version catalog used across all Gradle build files in the multi-module project.
• objectbox-java-api/src/main/java/io/objectbox/annotation/Entity.java — Core annotation defining ObjectBox entity schema; essential for understanding data model patterns across the codebase.
• objectbox-android/src/main/java/io/objectbox/android/ObjectBoxLiveData.java — Android-specific reactive integration layer; demonstrates primary pattern for reactive data binding in this platform.
• build-logic/src/main/kotlin/objectbox.publishing-conventions.gradle.kts — Shared publishing conventions for Maven Central; required reading for release and versioning workflows.

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.

Clone and build using Gradle wrapper: git clone https://github.com/objectbox/objectbox-java.git && cd objectbox-java && ./gradlew build. Verify Java/Kotlin toolchain is installed. No Maven or npm evident; Gradle is th…

Daily commands:

Inferred from Gradle structure: ./gradlew build compiles all modules; ./gradlew test runs tests (not visible in file list, but standard); ./gradlew publishToMavenLocal publishes artifacts locally. Android module r…

…shortened for this brief.

Key cautions & unknowns

• Small team — 3 contributors active in recent commits
• Single-maintainer risk — top contributor 94% of recent commits
• Scorecard: default branch unprotected (0/10)
• Android module has conditional build variants (adminIncluded vs. adminExcluded) that may cause unexpected behavior if admin UI is excluded from a build—verify variant selection in build.gradle.kts. ProGuard rule file…
• 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
• OpenSSF Scorecard

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.