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 #262) with another security suggestion!
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.
The security policy can be found by users who enter the project's "Security" panel. Having a policy file also adds references to it in the "New issue" page.
There are two main ways to receive such disclosures:
register an email or website available to receive such reports; and/or
Click "Enable" for "Private vulnerability reporting (Beta)"
I'll send a PR with a draft policy along with this issue. You could also create a https://github.com/rust-num/.github repository and add the policy there, in which case the policy will be available in all of the org's projects.
The text was updated successfully, but these errors were encountered:
Hey, it's Pedro and I'm back (see #262) with another security suggestion!
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.
The security policy can be found by users who enter the project's "Security" panel. Having a policy file also adds references to it in the "New issue" page.
There are two main ways to receive such disclosures:
If you want to use GitHub's reporting system, it must be activated for the repository:
I'll send a PR with a draft policy along with this issue. You could also create a https://github.com/rust-num/.github repository and add the policy there, in which case the policy will be available in all of the org's projects.
The text was updated successfully, but these errors were encountered: