You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, it's Pedro and I'm back (see emscripten-core/emscripten#19037), this time suggesting that emsdk also adopt a security policy.
A security policy (SECURITY.md) is a simple document that explains how the project wishes to receive and handle responsible disclosure of potential vulnerabilities. GitHub recommends that projects have one.
There are a few other ways to receive such disclosures (emails, websites, GitHub's vuln reporting feature), but I believe the solution used for emscripten itself (linking to the Chromium security bug tracker) would also be entirely reasonable for emsdk.
I'll send a PR with a draft policy (similar to emscripten's) along with this issue.
The text was updated successfully, but these errors were encountered:
Hey, it's Pedro and I'm back (see emscripten-core/emscripten#19037), this time suggesting that emsdk also adopt a security policy.
A security policy (SECURITY.md) is a simple document that explains how the project wishes to receive and handle responsible disclosure of potential vulnerabilities. GitHub recommends that projects have one.
There are a few other ways to receive such disclosures (emails, websites, GitHub's vuln reporting feature), but I believe the solution used for emscripten itself (linking to the Chromium security bug tracker) would also be entirely reasonable for emsdk.
I'll send a PR with a draft policy (similar to emscripten's) along with this issue.
The text was updated successfully, but these errors were encountered: