Entity resolution, also known as Data Matching or Record linkage is the task of finding a data set that refer to the same or similar real entity across different digital entities present on same or different data sets. Record linking is necessary when joining different entities which are similar and may or may not share some common identifiers. Neo4j offers various advantages to perform entity resolution / record linking. This repository covers such a use case of linking similar user accounts f
active 2023-09-14 → 2025-10-21 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 769 days from 2023-09-14 to 2025-10-21. Pushes: 2 total, peak 1 in a day. Pull requests: 13 total, peak 1 in a day. Issues: 0 total, peak 0 in a day. Comments: 1 total, peak 1 in a day. Stars: 20 total, peak 1 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 |
|---|---|---|---|---|
| neo4j-oss-build | 13 | 1 | 12 | 0 |
| jexp | 3 | 1 | 1 | 0 |
| msenechal | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 20 stars here means stars gained during the window, not the repo's star count.