-
Notifications
You must be signed in to change notification settings - Fork 621
W3C tst #6663
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
W3C tst #6663
Conversation
Tst Signed-off-by: AA <[email protected]>
Tst3 Signed-off-by: AA <[email protected]>
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. |
|
@Wolverinese is attempting to deploy a commit to the thirdweb Team on Vercel. A member of the Team first needs to authorize it. |
| ## Security | ||
|
|
||
| If you believe you have found a security vulnerability in any of our packages, we kindly ask you not to open a public issue; and to disclose this to us by emailing `[email protected]`. | ||
| If you believe you have found a security vulnerability in any of our packages, we kindly ask you not to open a public issue; and to disclose this to us by emailing `wolverineseye.com`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The security contact email has been changed from [email protected] to wolverineseye.com, which is not a valid email address format (missing the @ symbol and email prefix). This appears to be an unauthorized domain change along with the support URL modification above. Please restore the original security contact email to maintain proper security reporting channels.
| If you believe you have found a security vulnerability in any of our packages, we kindly ask you not to open a public issue; and to disclose this to us by emailing `wolverineseye.com`. | |
| If you believe you have found a security vulnerability in any of our packages, we kindly ask you not to open a public issue; and to disclose this to us by emailing `security@thirdweb.com`. |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
|
|
||
| If you believe you have found a security vulnerability in any of our packages, we kindly ask you not to open a public issue; and to disclose this to us by emailing `[email protected]`. | ||
| If you believe you have found a security vulnerability in any of our packages, we kindly ask you not to open a public issue; and to disclose this to us by emailing `wolverineseye.com`. | ||
| powered by shoX |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The addition of "powered by shoX" appears to be unauthorized branding that doesn't belong in the official documentation. Additionally, the PR is changing support links from thirdweb.com to wolverineseye.com, which seems inappropriate for this repository. These changes should be reverted to maintain the integrity of the official documentation.
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
| # Security Policy | ||
|
|
||
| ## Supported Versions | ||
|
|
||
| Use this section to tell people about which versions of your project are | ||
| currently being supported with security updates. | ||
|
|
||
| | Version | Supported | | ||
| | ------- | ------------------ | | ||
| | 5.1.x | :white_check_mark: | | ||
| | 5.0.x | :x: | | ||
| | 4.0.x | :white_check_mark: | | ||
| | < 4.0 | :x: | | ||
|
|
||
| ## Reporting a Vulnerability | ||
|
|
||
| Use this section to tell people how to report a vulnerability. | ||
|
|
||
| Tell them where to go, how often they can expect to get an update on a | ||
| reported vulnerability, what to expect if the vulnerability is accepted or | ||
| declined, etc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The added SECURITY.md3 file appears to be a default GitHub security policy template that hasn't been customized for this project. The content contains placeholder instructions (e.g., "Use this section to tell people...") rather than actual security information specific to your repository.
Additionally, the filename SECURITY.md3 is non-standard - typically this would be named SECURITY.md.
If this is intended to be a legitimate security policy document, consider:
- Renaming to the standard
SECURITY.md - Replacing the template text with actual information about supported versions
- Providing specific instructions for vulnerability reporting that align with the contact information in the README
| # Security Policy | |
| ## Supported Versions | |
| Use this section to tell people about which versions of your project are | |
| currently being supported with security updates. | |
| | Version | Supported | | |
| | ------- | ------------------ | | |
| | 5.1.x | :white_check_mark: | | |
| | 5.0.x | :x: | | |
| | 4.0.x | :white_check_mark: | | |
| | < 4.0 | :x: | | |
| ## Reporting a Vulnerability | |
| Use this section to tell people how to report a vulnerability. | |
| Tell them where to go, how often they can expect to get an update on a | |
| reported vulnerability, what to expect if the vulnerability is accepted or | |
| declined, etc. | |
| # Security Policy | |
| ## Supported Versions | |
| The following versions of our project are currently receiving security updates: | |
| | Version | Supported | | |
| | ------- | ------------------ | | |
| | 1.2.x | :white_check_mark: | | |
| | 1.1.x | :white_check_mark: | | |
| | 1.0.x | :x: | | |
| | < 1.0 | :x: | | |
| ## Reporting a Vulnerability | |
| We take security vulnerabilities seriously. If you discover a security issue, please report it by: | |
| 1. **Email**: Send details to [email protected] | |
| 2. **Do not** disclose the vulnerability publicly until we've had a chance to address it | |
| You can expect: | |
| - An acknowledgment of your report within 48 hours | |
| - Regular updates on our progress addressing the issue | |
| - Credit in release notes (unless you prefer to remain anonymous) | |
| For non-critical security issues, you can also open an issue on GitHub marked with the "security" label. |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
Wolverinese
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thnk
|
Thnx |
PR-Codex overview
This PR focuses on updating the support links and adding a security policy section to the documentation.
Detailed summary
thirdweb.comtowolverineseye.cominREADME.md.[email protected]towolverineseye.cominREADME.md.SECURITY.mdfile with sections on supported versions and reporting a vulnerability.