Badge not displayed in JSR, Deno and jsDelivr

[regseb]

Are you experiencing an issue with...

shields.io

🐞 Description

This badge is displayed in GitHub and npm, but it's not displayed in JSR, Deno and jsDelivr.

If I open this address in a browser, I get the following error:

Sorry, you have been blocked

You are unable to access shields.io

Why have I been blocked?

This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data.

What can I do to resolve this?

You can email the site owner to let them know you were blocked. Please include what you were doing when this page came up and the Cloudflare Ray ID found at the bottom of this page.

Performance & security by Cloudflare

🔗 Link to the badge

https://img.shields.io/endpoint?label=coverage&url=https%3A%2F%2Fbadge-api.stryker-mutator.io%2Fgithub.com%2Fregseb%2Fjfather%2Fmain

💡 Possible Solution

Others badges work:

• https://img.shields.io/npm/dm/jfather?label=npm&logo=npm&logoColor=whitesmoke
• https://img.shields.io/github/actions/workflow/status/regseb/jfather/ci.yml?branch=main&logo=github&logoColor=whitesmoke
• https://img.shields.io/badge/semver-2.0.0-blue?logo=semver&logoColor=whitesmoke

Perhaps the problem is with the endpoint route, as it needs to call another URL (https://badge-api.stryker-mutator.io/github.com/regseb/jfather/main). Cloudflare blocks because it detects a URL within a URL.

[github-actions]

Badge tested using npm run badge https://img.shields.io/endpoint?label=coverage&url=https%3A%2F%2Fbadge-api.stryker-mutator.io%2Fgithub.com%2Fregseb%2Fjfather%2Fmain
Output is available here

[chris48s]

Hi. As noted in #10981 (comment) I've temporarily blocked most traffic to the endpoint badge. This is intended to be a temporary measure, but I can't completely unblock it until the abusive traffic is under control.

[chris48s]

The majority of legitimate requests to the endpoint badge should now be getting served.

I'm not going to disclose the precise details of what we are/aren't blocking at the moment as we are still blocking a lot of unwanted traffic and I don't want to make it public how to circumvent that, but the majority of legitimate requests should now be unblocked.

I'm going to close these issues but we will continue to monitor the situation.