Add 'blocklisted' attribute to package version response

[fantastisch]

This PR adds a the boolean attribute blocklisted to a package version.

The reason for this contribution is that I am setting up a local dbt package index / registry within my organization private cloud. I am aware of the ability to host the Middleman app ourselves. However, the technology used does not really match my organization's preferred technology stack. Our current approach is to download all "jsons" from https://hub.getdbt.com/api/v1/ and hosts these as static files, and just rewrite the source tarball URLs. This works wonderful, except when implementing this solution we found that blocklisted packages are still downloadable from the dbt Package Hub. My organization prefers not to have the ability to work with blocklisted packages at all, hence our wish to remove the blocklisted packages. We can of course fetch the blocklist from GitHub and implement logic to remove the blocklisted packages. However, if we can just get this from the already existing REST api, by adding the blocklisted attribute for every package version, we have an even simpler solution that other organization trying to achieve the same can could benefit from. Also, if dbt Labs ever changes the blocklist logic, e.g. to block specific package versions, our implementation would not be affected.

[vercel]

@mlacroix-bolcom is attempting to deploy a commit to the dbt-labs Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hub-getdbt-com	Ready	Preview, Comment	Feb 2, 2026 10:57pm

[joellabes]

Makes sense! I have checked and adding additional keys to the version dict is OK as long as it's repeated in all entries (source), which is the case here. So happy to get this merged in 🚀