tedious 20.3.0 → 20.3.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -0
- package/SECURITY.md +23 -0
- package/lib/connection.js +2 -9
- package/lib/connection.js.map +1 -1
- package/lib/request.js +5 -1
- package/lib/request.js.map +1 -1
- package/lib/token/handler.js +9 -1
- package/lib/token/handler.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -53,6 +53,9 @@ We'd like to learn more about how you use tedious:
|
|
|
53
53
|
## Contributing
|
|
54
54
|
We welcome contributions from the community. Feel free to checkout the code and submit pull requests.
|
|
55
55
|
|
|
56
|
+
## Security
|
|
57
|
+
Please report security vulnerabilities privately. See our [security policy](SECURITY.md) for reporting instructions.
|
|
58
|
+
|
|
56
59
|
<a name="license"></a>
|
|
57
60
|
## License
|
|
58
61
|
|
package/SECURITY.md
ADDED
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
# Security Policy
|
|
2
|
+
|
|
3
|
+
## Reporting a Vulnerability
|
|
4
|
+
|
|
5
|
+
Please report suspected security issues in Tedious privately using
|
|
6
|
+
[GitHub's private vulnerability reporting](https://github.com/tediousjs/tedious/security/advisories/new).
|
|
7
|
+
You can also open the repository's **Security** tab, select **Advisories**, and
|
|
8
|
+
click **Report a vulnerability**.
|
|
9
|
+
|
|
10
|
+
Do not disclose vulnerabilities in public issues, discussions, or pull requests.
|
|
11
|
+
Reports submitted through this process are private and are not automatically
|
|
12
|
+
published as security advisories.
|
|
13
|
+
|
|
14
|
+
Include the following details where possible:
|
|
15
|
+
|
|
16
|
+
- A description of the vulnerability and its potential impact.
|
|
17
|
+
- The affected Tedious version and relevant environment details.
|
|
18
|
+
- Steps to reproduce the issue or a minimal proof of concept.
|
|
19
|
+
- Any suggested fix or workaround.
|
|
20
|
+
|
|
21
|
+
Do not include credentials, secrets, or sensitive customer data in your report.
|
|
22
|
+
Use the private report to discuss the issue with the maintainers and coordinate
|
|
23
|
+
any public disclosure.
|