DozerDb Core Plugin Functionality - Enhances Neo4j Community Edition with enterprise features.
active 2023-09-15 → 2026-03-18 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 916 days from 2023-09-15 to 2026-03-18. Pushes: 29 total, peak 6 in a day. Pull requests: 8 total, peak 2 in a day. Issues: 54 total, peak 3 in a day. Comments: 136 total, peak 8 in a day. Stars: 42 total, peak 2 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| jmsuhy | 153 | 29 | 7 | 84 |
| Johnno1011 | 11 | 0 | 0 | 9 |
| rg2609 | 11 | 0 | 0 | 7 |
| awhillas | 8 | 0 | 0 | 6 |
| irwansb | 6 | 0 | 1 | 4 |
| f1-outsourcing | 4 | 0 | 0 | 4 |
| kushankurdas | 4 | 0 | 0 | 2 |
| Zeppier | 3 | 0 | 0 | 3 |
| janakmistry | 3 | 0 | 0 | 1 |
| tsetso-spread | 3 | 0 | 0 | 2 |
| irwangunardi | 2 | 0 | 0 | 1 |
| kaumudpa | 2 | 0 | 0 | 1 |
| agsgde | 2 | 0 | 0 | 1 |
| alexanoid | 2 | 0 | 0 | 2 |
| alextsakpinis | 2 | 0 | 0 | 2 |
| shaswatbedrock | 1 | 0 | 0 | 0 |
| Bligoubloups | 1 | 0 | 0 | 1 |
| pippascroggins | 1 | 0 | 0 | 0 |
| tomksck | 1 | 0 | 0 | 0 |
| Abutler101 | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#37tsetso-spread2026-03-18 10:13Fix ClassCastException in ConstraintChecker.STORAGE_READER_CONSTRAINT_BUILDER
- Issue comment#31rickross2025-09-06 12:01Add Role based access control
- Issue comment#35jmsuhy2025-07-24 21:50Property existence constraint does not work
- Issue comment#35anthony22612025-07-23 09:06Property existence constraint does not work
- Issue comment#33jmsuhy2025-06-26 20:43Neo.DatabaseError.Database.Unknown "Unable to complete transaction."
- Issue#33jmsuhy2025-06-26 20:43Neo.DatabaseError.Database.Unknown "Unable to complete transaction."
- Issue comment#35agsgde2025-03-18 09:08Property existence constraint does not work
- Issue comment#35jmsuhy2025-03-17 16:33Property existence constraint does not work
- Issue#35agsgde2025-03-17 11:20Property existence constraint does not work
- Issue comment#34Johnno10112025-02-27 00:07DozerDB 5.26.3.0 Cannot DROP DATABASE with Python SDK
- Issue comment#34jmsuhy2025-02-26 22:35DozerDB 5.26.3.0 Cannot DROP DATABASE with Python SDK
- Issue comment#34jmsuhy2025-02-26 20:25DozerDB 5.26.3.0 Cannot DROP DATABASE with Python SDK
- Issue#34Johnno10112025-02-26 10:42DozerDB 5.26.3.0 Cannot DROP DATABASE with Python SDK
- Issue comment#32Johnno10112025-02-25 12:09Use of parameters via python driver seems to break Dozer enhanced images
- Issue comment#26jmsuhy2025-02-24 21:03Implement node and relationship property type constraint
- Pull request#26jmsuhy2025-02-24 21:03
- Issue comment#33jmsuhy2025-02-24 21:00Neo.DatabaseError.Database.Unknown "Unable to complete transaction."
- Issue comment#11jmsuhy2025-02-24 20:57Multiple databases beyond 100
- Issue comment#32jmsuhy2025-02-24 20:57Use of parameters via python driver seems to break Dozer enhanced images
- Issue#32jmsuhy2025-02-24 20:57Use of parameters via python driver seems to break Dozer enhanced images
- Issue comment#11jmsuhy2025-02-08 03:28Multiple databases beyond 100
- Issue comment#33jmsuhy2025-02-08 01:53Neo.DatabaseError.Database.Unknown "Unable to complete transaction."
- Issue comment#11jmsuhy2025-02-07 22:07Multiple databases beyond 100
- Issue#11jmsuhy2025-02-07 22:07Multiple databases beyond 100
- Issue comment#11jmsuhy2025-02-05 15:14Multiple databases beyond 100
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 42 stars here means stars gained during the window, not the repo's star count.