'Why is unpkg suddenly unavailable (403) for my scope when it was previously available

I have been using unpkg for a while and started working on my new UI. I have the following public npm package (https://www.npmjs.com/package/@jrg/core-ui) but when I got to (https://unpkg.com/browse/@jrg/core-ui@latest) it gets redirected to the proper version (0.0.28) but I get a 404. Also if I try to go to my scope (which used to work) I get a 403.

When I install locally using npm everything installs correctly...

$ ls node_modules/@jrg/core-ui 
Base.mjs                README.md               build                   jsdoc.conf.json         rollup.config.mjs
LICENSE                 ShadowElement.mjs       index.mjs               package.json

Why would my unpkg site become suddenly unavailable?

npm unpkg

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source

'Why is unpkg suddenly unavailable (403) for my scope when it was previously available

Sources

Related Questions