Work on issues not on marketing

[WolfgangFahl]

https://www.linkedin.com/comm/feed/update/urn:li:activity:7479891717509455872

popped up this morning and led here. Given this project has not even 1000 stars - open tickets are months old and not worked on i feel the priorities are inadequate.

[WolfgangFahl]

To ground this with current numbers (as of 2026-07-11):

Issue tracker

• 34 open / 29 closed issues, 0 open PRs
• 32 of 34 open issues have zero comments — no maintainer reply
• 33 of 34 have had no update in >6 months
• The 5 oldest (Implement Editing for Records in Dashboard #26, Aggregate aliases for relationships #27, Implement UNSAFE Cypher Query Runner for self-hosted setups #30, Implement Upsert method by specified props to be matched #39, Implement schema based validation on the backend on-the-fly (instead of series of tx requests on the sdk side) #43) are from January 2025 (~18 months) and untouched since

Codebase, same window

• Actually very active: last push 2026-07-10, releases roughly every 1–2 days (v2.10.0 on 2026-07-09), 313★

So the code ships fast, but the public issue tracker gets almost no engagement, while there is clear investment in marketing/narrative (the founder LinkedIn retrospective that led me here, linking a dev.to story). For a <1k-star project, triaging and answering filed issues would build more trust than more storytelling — that is the priority mismatch I am flagging.