flowable/flowable-engine vs hollischuang/tobetopjavaer
flowable/flowable-engine shows stronger signals overall
As of June 2026, flowable-engine shows healthier maintenance signals than tobetopjavaer. flowable-engine rates Healthy overall while tobetopjavaer rates Concerns. flowable-engine last saw a commit 1 month ago with 12+ active contributors, while tobetopjavaer last saw a commit 2 years ago with 15+ active contributors. Neither has known critical or high-severity CVEs in its dependency tree.
Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.
flowable/flowable-engine →
Healthy across the board
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
No critical CVEs, sane security posture — runnable as-is.
- ⚠No test directory detected
- ✓Last commit 2d ago
- ✓12 active contributors
- ✓Distributed ownership (top contributor 47% of recent commits)
- ✓Apache-2.0 licensed
- ✓CI configured
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
hollischuang/tobetopjavaer →
Stale and unlicensed — last commit 2y ago
no license — legally unclear; last commit was 2y ago…
no license — can't legally use code; no tests detected…
Documented and popular — useful reference codebase to read through.
no license — can't legally use code; last commit was 2y ago…
- ⚠Stale — last commit 2y ago
- ⚠No license — legally unclear to depend on
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓15 active contributors
- ✓Distributed ownership (top contributor 34% of recent commits)
What would improve this?
- →Use as dependency Concerns → Mixed if: publish a permissive license (MIT, Apache-2.0, etc.)
- →Fork & modify Concerns → Mixed if: add a LICENSE file
- →Deploy as-is Concerns → Mixed if: add a LICENSE file
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
Signal-by-signal breakdown
| flowable-engine | tobetopjavaer | |
|---|---|---|
| Stars | 9,241 | 25,426 |
| Last commit | 1mo ago | 2y ago |
| License | Apache-2.0 | — |
| Open issues | 398 | 61 |
| Has tests | — | — |
| Has CI | ✓ | — |
| Test coverage | — | — |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Concerns signals |
Want the full analysis? flowable/flowable-engine · hollischuang/tobetopjavaer
Ask AI about flowable/flowable-engine vs hollischuang/tobetopjavaer
Open the chat with a comparison question pre-filled.