Forking and Continuity Planning

[bcholmes]

A few people have posted here asking some variation of "is this project dead?" I think it's pretty obvious that the original creator isn't engaged any more. It's been a year and a half since the codebase changed, and Hopding's GitHub activity for the last year is empty. If Hopding has simply stepped away, we could try to encourage Hopding to add some additional maintainers. But otherwise it feels like it might be time to fork.

So the next question is: is anyone taking on a supported fork? There are almost 500 forks of this repo, but none of them stand out as highly active. There's clearly a lot of activity in the issues and pull requests: the gap is in maintenance.

npm lists two forks that seem significant:

• pdf-lib-plus-encrypt
• pdf-lib-draw-svg (which appears to be based on 1.16.x of pdf-lib).

I haven't contributed code, here. Like many, I'm a consumer of this library, and want to see it survive. But I'd love to have a conversation about ensuring the continuity of this library.