Missing firewall domains for Deno ecosystem: esm.sh, cdn.jsdelivr.net

[Mossaka]

Summary

In the AWF Build/Test Experiment v3 (Feb 17, 2026), several Deno repos failed to build because key CDN domains used by the Deno ecosystem are not in the firewall allowlist.

Good news: jsr.io and deno.land have been added since v2 — this fixed oak and improved other repos.

Missing Domains

Domain	Repos Affected	Usage
esm.sh	saaskit, fresh	ESM CDN used by Fresh framework and Deno projects for importing npm packages
cdn.jsdelivr.net	lume	CDN used by Lume static site generator for Deno module distribution

Impact

• 3 Deno repos cannot build at all (lume, saaskit fail completely; fresh partially affected)
• These domains are fundamental to the Deno ecosystem, used by many projects beyond our test set

Suggestion

Add to the Deno/node ecosystem domain allowlist:

• esm.sh
• cdn.jsdelivr.net

Experiment Context

• gh-aw: v0.45.2, AWF: v0.19.1
• Deno overall: 7/10 builds succeed, would likely improve to 9-10/10 with these domains
• Full report: AWF Build/Test Experiment v3 (Feb 17, 2026)

[github-actions]

👋 Hello! I noticed this issue is part of a series of related reports from the AWF Build/Test Experiment v3 (Feb 17, 2026):

• Java builds fail 0/10: Maven Central and Gradle Plugin Portal unreachable through Squid proxy #946 - Java ecosystem: Maven Central and Gradle Plugin Portal proxy issues (domains ARE in allowlist but still unreachable)
• Missing firewall domains for Deno ecosystem: esm.sh, cdn.jsdelivr.net #947 (this issue) - Deno ecosystem: Missing CDN domains (esm.sh, cdn.jsdelivr.net)
• Missing crates.io/static.rust-lang.org in Python and Deno ecosystem allowlists #950 - Python/Deno ecosystem: Missing Rust registry domains for cross-language projects (crates.io, static.rust-lang.org)

These are companion issues, not duplicates — each addresses different ecosystems and specific domain/proxy challenges identified in the same experiment.

---

This is an automated message from the issue duplication detector. These issues may benefit from coordinated resolution since they're part of the same testing initiative.

AI generated by Issue Duplication Detector

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

AI generated by Issue Monster

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

AI generated by Issue Monster

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

AI generated by Issue Monster

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

AI generated by Issue Monster

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

AI generated by Issue Monster

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

AI generated by Issue Monster

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

AI generated by Issue Monster

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

AI generated by Issue Monster

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster