forked from nextauthjs/next-auth
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: match docs page wording for
SECURITY.md
- Loading branch information
1 parent
0431c2a
commit 2670bbb
Showing
1 changed file
with
8 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,12 +2,6 @@ | |
|
||
NextAuth.js practices responsible disclosure. | ||
|
||
## Supported Versions | ||
|
||
Security updates are only released for the current version. | ||
|
||
Old releases are not maintained and do not receive updates. | ||
|
||
## Reporting a Vulnerability | ||
|
||
We request that you contact us directly to report serious issues that might impact the security of sites using NextAuth.js. | ||
|
@@ -19,6 +13,12 @@ If you contact us regarding a serious issue: | |
- We will disclose the issue (and credit you, with your consent) once a fix to resolve the issue has been released. | ||
- If 90 days has elapsed and we still don't have a fix, we will disclose the issue publicly. | ||
|
||
Currently, the best way to report an issue is by contacting us via email at me@iaincollins.com or info@balazsorban.com and [email protected]. | ||
The best way to report an issue is by contacting us via email at info@balazsorban.com or me@iaincollins.com and [email protected], or raise a public issue requesting someone get in touch with you via whatever means you prefer for more details. (Please do not disclose sensitive details publicly at this stage.) | ||
|
||
For less serious issues (e.g. RFC compliance for unsupported flows or potential issues that may cause a problem future or default behaviour / options) it is appropriate to submit these these publically as bug reports or feature requests or to raise a question to open a discussion around them. | ||
> For less serious issues (e.g. RFC compliance for unsupported flows or potential issues that may cause a problem in the future) it is appropriate to submit these these publically as bug reports or feature requests or to raise a question to open a discussion around them. | ||
## Supported Versions | ||
|
||
Security updates are only released for the current version. | ||
|
||
Old releases are not maintained and do not receive updates. |