Skip to content

chore(server): document why crossOriginEmbedderPolicy is disabled (#350) #351

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CryptoJones merged 1 commit into from
May 19, 2026
Merged

chore(server): document why crossOriginEmbedderPolicy is disabled (#350) #351

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions server.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,16 @@ if (trustProxy === 'true') {
// legitimate clients hitting the docs endpoint or future
// browser-based dashboards. Operators who add an HTML surface
// can re-enable via HELMET_CSP=1.
//
// crossOriginEmbedderPolicy is also disabled: Swagger UI at /docs
// loads its JS/CSS bundle from the package's own host but pulls
// theme assets cross-origin, and helmet's default
// `require-corp` value blocks any sub-resource that doesn't
// explicitly opt into CORP/CORS — which would break the docs
// page on first load. Since this API has no other browser-facing
// HTML, leaving COEP off is the lower-risk choice. Operators
// hosting embedded dashboards alongside the API should configure
// helmet directly rather than re-enabling COEP at this layer.
app.use(helmet({
contentSecurityPolicy: process.env.HELMET_CSP === '1' ? undefined : false,
crossOriginEmbedderPolicy: false,
Expand Down