Could you add a lastupdated key to meta.json?

[georgestephanis]

I figure if folks keep a record of when they last pulled the data, this could make it simpler to abort early if the files hashes hadn't been updated since.

(I suppose it could be done by comparing the filenames / hashes as well, but a timestamp or date string would be nice to know how recent the builds are)

[CodeAlDente]

Hi @georgestephanis, thanks for the suggestion! That makes sense. I’ll add the date of last update and also include more meta info, like the number of lines and file size. This can also be used to reintroduce the shields badges.

[CodeAlDente]

It's completed in 20d22b8. In the next list update, meta.json will be updated with the information.

[georgestephanis]

@CodeAlDente Also, I've built a WordPress plugin that caches a local copy of this in the database for reference and querying against -- would that be at all useful if it were polished up with some phpdoc and made public for you to link to as an example client? (GPL licensed, so just publicly available for whatever)

[CodeAlDente]

Sounds good — as long as you don’t ship the list with the plugin, it’s good to go. Just make sure users fetch the list themselves, programmatically using the meta.json, so the list isn’t bundled but only used by the plugin.

Just a heads-up: starting August 1st, 2025, any commercial use will officially require a separate paid commercial license — so please highlight that in your docs or README too.

For more information, please read this: 🔗 Upcoming License Change