Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

WebAssembly.Memory causes issues with content security policy

Open
#268 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, wasm
Domain
security, web-dev

Research direction

Start by reproducing the Safari error while loading sql.js under a script-src policy without 'unsafe-eval'. Read the linked WebAssembly CSP proposal and compare its guidance with the reported WebAssembly.Memory behavior. Done means identifying a viable workaround or clearly documenting that Safari cannot support this configuration.

Written by the indexing model from the issue text.

Description

Safari throws an error when loading with a content security policy that doesn't include 'unsafe-eval' in script-src. It seems to be the odd man out. I don't know what can be done to work around it.

https://github.com/WebAssembly/content-security-policy/blob/master/proposals/CSP.md

web-assembly-csp

Dominant language
JavaScript
Stars
13.7k
Forks
1.1k
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sql-js/sql.js

All issues in sql-js/sql.js

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.