We answer one question about running applications: "which code actually ran when this API was called?"
한국어 안내는 Reqover 한국어 README에 있습니다.
A coverage tool tells you OrderService.find() ran. It does not tell you who ran it — GET /orders/{id}? an admin batch? both? So after changing one shared method, deciding which APIs to retest usually comes down to reading code by hand.
We record that missing dimension at runtime: from the moment a request arrives until the response leaves, the methods that request actually walked through, kept separate per request.
reqover — for Spring MVC and WebFlux applications.
- Per-request execution records — each request gets its own bucket, so one API's path never blends into another's
- No source changes — a Java agent inserts the recording calls at startup, only in the packages you name
- Both directions — API → code report, and code → API reverse lookup for deciding where to retest
- Survives thread hops — WebFlux moves a single request across threads; attribution follows it
| Try it in 5 minutes | Run the demo application |
| See what it produces | Three things the report shows |
| Wire it into your app | Spring integration guide |
| Know the limits first | What works / what doesn't |
| Download | Latest release |
Note
Reqover is an early development release, built for development, QA, and staging rather than permanent production use. It records method entry, not lines or branches, and it does not replace JaCoCo — the two answer different questions.
- Apache-2.0 for everything we write
- Limits stated up front — the README has a "what doesn't work" section, because using a tool with the wrong expectations wastes everyone's time
- Reproducible checks — JDK 17 and 21 CI matrix, plus E2E tests that attach the agent in a separate JVM
- Dependency transparency — a CycloneDX SBOM and a vulnerability-check script live in the repository
- Bilingual docs — English is primary, Korean is maintained alongside
This is a small project, so anything helps. The most useful contribution right now is a report saying "I ran the demo and it didn't work" — including your OS, JDK version, the exact command, and what actually happened.
Good first issues · Contributing Guide · Code of Conduct
Issues, pull requests, and commit messages are written in English. Questions in Korean are welcome — just add an English summary so others can follow along.
Caution
Do not report security vulnerabilities in public issues. Use the private reporting process in the Security Policy.
| Name | GitHub | |
|---|---|---|
| TaeHui Kim | @TaeHuiKKIM | TaeHui Kim |
| Sangmin Lee | @lsmin3388 | Sangmin Lee |
Reqover started as an entry for the 2026 Korea Open Source Developer Competition, and we intend to keep maintaining it past the contest.