You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We took over this library since it was not getting security updates in a timely manner. It's been a good couple of years of keeping the lights on while making some important accessibility enhancements.
My small team and I don't have the capacity to handle maintaining this library anymore. That includes even the relatively minor aspect of releasing security fixes.
So we'll be inviting others to take on this library.
Are you looking to augment your team or someone to take over in its entirety? What does the LOE look like for the project now to maintain security updates?
What about using renovate to help automate the work?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hey @dgreene1, I would be glad to become a maintainer for this library.
A little bit about my experience:
I’ve worked as a frontend developer for the last 10+ years. For the last 6 years, I’ve worked extensively with React. That’s how I first learned about this library - I used it in one of my projects.
I write about open source and regularly search for issues to contribute to. I write about open issues in open-source projects, it is in ukrainean but you still can check it out: https://t.me/opensourceua
I would gladly work on the issue you mentioned — #220.
Has a maintainer been identified. I still have a few issues I’d like to not need to maintain separately but not sure the status here.
Sadly, no. No one has shown sufficient dedication in that I haven’t seen any issue be fixed. That’s why most of the issues in the repo have been cleared by stalebot. To protect users, I won’t be giving it away to just anyone since I would be upset if it were taken on by someone with nefarious intentions. That said I don’t plan to do anything other than the occasional security update release (if that). This library should therefore be considered to be deprecated. Forking and maintain on one’s own is a great choice. I apologize, but I no longer work on the UI regularly and my company longer uses this library either as we try very hard to avoid a tree when possible in our designs.
I saw your note above that no one had fixed any open issues yet, so I went through the issue tracker first and opened #255.
That pull request fixes the Cmd+H / collapsed tabbableId infinite loop in type-ahead keyboard navigation (#182), guards controlledSelectedIds and controlledExpandedIds against stale node IDs when filtering tree data (#191), adds onKeyDown to ITreeViewProps (#202), and exports ITreeNode from the package entrypoint (#218).
At Eclipse Technology (@eldertek), we actively maintain several TypeScript/React and web open source packages (including eldertek/duplicatefinder up to v1.10.10). We would be happy to take over maintenance and ownership of react-accessible-treeview under @eldertek (including React 19 peer dependency support, triage, and npm releases).
I recommend being wary of the user @eldertek. On 13 Nov at 11:56 GMT, @eldertek posted 10 GitHub comments in less than a minute, to 10 different repositories, offering to take over maintenance of those repositories. This calls into question why these requests are being automated, and why this user is so keen to take over unmaintained repositories. I am worried that this user is not authentically interested in helping with maintaining these repositories, but is rather attempting a supply chain attack.
Reminder to all, I’ll only be handing over maintainership to someone who demonstrates making PRs that come with all the required stuff and show emphasis on what matters to a repo like this.
Activity
jej2003 commentedon Jun 12, 2025
Are you looking to augment your team or someone to take over in its entirety? What does the LOE look like for the project now to maintain security updates?
What about using renovate to help automate the work?
dgreene1 commentedon Jun 12, 2025
Someone to take over. LOE is something like 2 hours a month.
robinsingh1 commentedon Jun 26, 2025
Hey @dgreene1 , I would be interested in helping maintain the repo. Would love to chat through next steps
stale commentedon Aug 25, 2025
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
stale commentedon Sep 1, 2025
This issue was closed automatically since it was marked as stale because it has not had recent activity. Thank you for your contributions.
dolgachio commentedon Nov 28, 2025
Hey @dgreene1, I would be glad to become a maintainer for this library.
A little bit about my experience:
I would gladly work on the issue you mentioned — #220.
jej2003 commentedon Jun 12, 2026
Has a maintainer been identified. I still have a few issues I’d like to not need to maintain separately but not sure the status here.
dgreene1 commentedon Jun 12, 2026
Sadly, no. No one has shown sufficient dedication in that I haven’t seen any issue be fixed. That’s why most of the issues in the repo have been cleared by stalebot. To protect users, I won’t be giving it away to just anyone since I would be upset if it were taken on by someone with nefarious intentions. That said I don’t plan to do anything other than the occasional security update release (if that). This library should therefore be considered to be deprecated. Forking and maintain on one’s own is a great choice. I apologize, but I no longer work on the UI regularly and my company longer uses this library either as we try very hard to avoid a tree when possible in our designs.
eldertek commentedon Nov 13, 2026
Hello @dgreene1,
I saw your note above that no one had fixed any open issues yet, so I went through the issue tracker first and opened #255.
That pull request fixes the
Cmd+H/ collapsedtabbableIdinfinite loop in type-ahead keyboard navigation (#182), guardscontrolledSelectedIdsandcontrolledExpandedIdsagainst stale node IDs when filtering tree data (#191), addsonKeyDowntoITreeViewProps(#202), and exportsITreeNodefrom the package entrypoint (#218).At Eclipse Technology (
@eldertek), we actively maintain several TypeScript/React and web open source packages (includingeldertek/duplicatefinderup tov1.10.10). We would be happy to take over maintenance and ownership ofreact-accessible-treeviewunder@eldertek(including React 19 peer dependency support, triage, and npm releases).Best regards,
Théo
vladh commentedon Nov 16, 2026
I recommend being wary of the user @eldertek. On 13 Nov at 11:56 GMT, @eldertek posted 10 GitHub comments in less than a minute, to 10 different repositories, offering to take over maintenance of those repositories. This calls into question why these requests are being automated, and why this user is so keen to take over unmaintained repositories. I am worried that this user is not authentically interested in helping with maintaining these repositories, but is rather attempting a supply chain attack.
The comments:
@eldertek has also offered to take over maintenance of my own repo, mpld3:
More information: agentscan.tools/user/eldertek
I am posting this comment to all affected repos.
dgreene1 commentedon Nov 16, 2026
Reminder to all, I’ll only be handing over maintainership to someone who demonstrates making PRs that come with all the required stuff and show emphasis on what matters to a repo like this.
Until then, this repo is effectively frozen.