I don’t see much of a problem with that. It’s a spec, and is probably considered complete by its authors. The issues and PRs are mostly people wanting to add links to more implementations of the spec to the README. That’s understandable but also not really necessary.
If you do not believe a PR or issue to be valid, you close it. If you are literally not willing to accept any PRs or issues, turn the feature off.
Either way, we don’t know if they really don’t want any issues or PRs opened at all just because they have some old issues and PRs still open.
(fyi, I am very happy user of ULID for years, I don't need libraries to be updated to keep using it)
I am wanting UUIDv7 but I can use ULID right now.
Since _every_ system has a down side or limitation, I am perfectly happy with ULID's flaws.
Why should there be disdain or dismissal of a system that solves many people's problems?
Most of the time, when I hear people talking about UUIDs being better than big ints, it comes down to big ints leaking data (how many users / posts / comments your site has) and letting an attacker fetch sequential entries (user id 4 works, now try 5). This is even the reasoning in the supabase article. While ULIDs don't reveal the next entry, they do leak data (either creation date or number of entries, as all ULIDs are either prefixed with physical time or logical time).
Why don't we just encrypt / decrypt IDs when going over the wire (most API frameworks even have native methods to transform different types of data)? It suffers from neither issue above, is natively supported by API frameworks, and any time used on compute will be dwarfed by network latency. Is this already a pattern and I just don't know about it?
EDIT: ahh, below they list one advantage of UUIDs / ULIDs which is you can generate client side. That is reasonable.
In the end support for something this simple and complete isn’t something I’d have big concerns about.
I went through this exploration a while back for a new project and decided on uuidv7s, which are binary compatible with ULIDs but will likely find more support as they get added to the original UUID RFC.
Either UUIDv7 or XIDs seem like better choices than ULIDs for new projects.
* Supabase on different primary key considerations: https://supabase.com/blog/choosing-a-postgres-primary-key
* Postgres extension for generating various kinds of IDs: https://github.com/VADOSWARE/pg_idkit