hibernate-orm
Idiomatic persistence for Java and relational databases
Runssource: GitHubhomepageJavaApache-2.0commit e1f9fc665890
Java, Apache-2.0 licensed. The project labels itself: database, envers, hibernate, hibernate orm, jakarta persistence, jakartaee, java and jdbc.
hibernate-orm runs. An Argusic agent installed it in 22 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Hibernate ORM builds with JDK 25 and Gradle 9.7.1; hibernate-core test suite passes all 18115 tests against H2 embedded database with 0 failures.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No JDK installed in container2 minutes
- unzip not available (no root access), blocking SDKMAN install1 minute
- Gradle daemon worker shutdown race at end of test run (Could not stop all services)
- Install time
- 22 minutes
- Cold machine to finish
- 24 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- ./gradlew --rerun-tasks :hibernate-core:test completed 18115 tests with 0 failures 0 errors (gradlew tasks, compileJava, and full compileJava also succeeded); test XML parsing confirmed 0 failures across all 3639 suite files
- Model tokens used
- 136,164
- Exact commit tested
- e1f9fc665890
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
2. `unzip` missing (system package, no root) → worked around by using tar.gz distribution directly
3. Gradle daemon shutdown race ("Could not stop all services") at test completion → not a test fail…
The build failure after "BUILD FAILED" is only the Gradle daemon failing to cleanly stop its worker…
tokens used
136,164
I now have all the data I need. Let me compose the final result.
**Duration**: The build and test run took ~22 minutes total (started ~23:29, test results timestamp…
**Errors encountered**:
1. No JDK installed → downloaded JDK 25 (Adoptium Temurin) manually via curl+tar since `unzip` wasn…
2. `unzip` missing (system package, no root) → worked around by using tar.gz distribution directly
3. Gradle daemon shutdown race ("Could not stop all services") at test completion → not a test fail…
The build failure after "BUILD FAILED" is only the Gradle daemon failing to cleanly stop its worker…Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Took 22 minutes to install, slower than the median of the 30 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 31 database projects Argusic has installed and timed, hibernate-orm was the 30th fastest to reach a running state, and 25 of 31 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
databaseenvershibernatehibernate-ormjakarta-persistencejakartaeejavajdbcjpaobject-relational-mapperobject-relational-mappingormpersistencepersistence-frameworksql
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/hibernate-orm)Questions
- Does hibernate-orm run?
- Yes. hibernate-orm runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test hibernate-orm?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e1f9fc665890. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test hibernate-orm?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does hibernate-orm take to install?
- 22 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does hibernate-orm need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing hibernate-orm?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does hibernate-orm compare with the alternatives?
- Of the 31 database projects Argusic has installed and timed, hibernate-orm was the 30th fastest to reach a running state, and 25 of 31 reached one at all.
- Where is the evidence for hibernate-orm?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.