javapathfinder / jpf-core
Code health
This codebase scores 7.7 out of 10 for code health, which we rate good. It also scores maintainability 7.7 and static performance 9.9 out of 10. The three are scored separately and never blended into one number.
Do next
1 thing worth doing this quarter.
Worth planning
Delete 206 unused symbols and files (21,114 lines)
Nothing in the graph reaches them, across 152 files; every reader and agent pays to skip them.
- symbols
- 206
- lines
- 21,114
- safe to delete
- Yes(inferred)
Medium effort
Improve what Repowise can see
Add a test coverage report
Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.
- line coverage
- Unknown, no report
Small effortReview the 36 proposed decisions
None is accepted yet, so nothing can drift from one and agents get no enforced guidance from them.
- proposed
- 36
- accepted
- 0
Medium effort
- Lines of code
- 127.5K
Recent activity
All commitsCommits
- df58f6e8feat: add Java 11 String.lines() method with tests (#611)2mo ago
- 5c12b8fafix: resolve windows platform specific URI formatting in FileTest testToURI testcase (#598)3mo ago
- 2bf98722Add unit tests for SimplePool (Fixes #585) (#592)6mo ago
- c450e0b3resource leaks fixed (#586)6mo ago
- f70927ceUse ZonedDateTime instead of LocalTime to handle midnight wrapping (#582)9mo ago
- 426be898Updated the redundant docs (#578)10mo ago
Decisions
- Treat Search as the heart of search classesproposed · 2mo ago
- Use a safety margin listener release on OutOfMemoryErrors to avoid memory leakproposed · 2mo ago
- Separate annotation type system from ClassInfosproposed · 2mo ago
- Encapsulate JPF-specific types by loading Verify-only dependencies on demandproposed · 2mo ago
- Provide mostly empty method bodies in Verify for execution outside JPF environmentproposed · 2mo ago
- Use Config to avoid structural bottlenecks from parameterized extensions needing to update a central Option classproposed · 2mo ago
Everything we found
2,730 open
Every detector's open count by area, each with its worst example. An inventory, not a to-do list: the actions above are the part worth doing.
- worst item is critical severity. Code health1,174Function hotspot · src/main/gov/nasa/jpf/jvm/ClassFile.java40 findings · 7.7 deducted
- worst item is medium severity. Refactoring156pushArguments+1.5 health, S effort · src/main/gov/nasa/jpf/jvm/bytecode/INVOKECG.java
- worst item is medium severity. Decisions36Optimize testRecursiveJoinThreadGroup performance36 awaiting review
- worst item is medium severity. Ownership1,137src/tests/gov/nasa/jpf/test/java/io/FileTest.java88% single-owner concentration, 1 commits in 90d
- worst item is low severity. Dead code227src/classes/modules/java.base/java/nio/files/spi/FileSystemProvider.javaUnreachable symbol (50 lines)
Composition
Open the graphExplore this codebase
- Docs2,243 pages across 4 modules
- ChatAsk this codebase a question and get an answer with its sources.
- Files1,280 files with per-file docs, health and history
- ArchitectureDependency graph, layers, and 10 entry points
- Code healthPer-file scores, 1,302 open findings, coverage and refactoring targets
- Knowledge graphEntities, communities, and the paths between them
- Change couplingFiles that keep changing together, mined from commit history
- CommitsChange-risk ranked history with agent provenance
- ContributorsBus factor, per-file maintainers, and the human/agent split
- StatsSize class, origin, lifetime churn, rhythm and records
- CostsWhat indexing this snapshot cost, by model and by run.