Revise security policy for reporting vulnerabilities

[Dargon789]

Updated contact information for vulnerability reporting. e90b2e6

Summary by Sourcery

Documentation:

• Update SECURITY.md to describe how to report vulnerabilities and provide the dev@wevm.dev contact address for disclosures.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
sequence-js-docs	Ready	Preview, Comment	Dec 30, 2025 5:11pm
sequence-js-web	Error		Dec 30, 2025 5:11pm
wagmi-project	Ready	Preview, Comment	Dec 30, 2025 5:11pm

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the security policy documentation to provide concrete instructions and contact information for reporting vulnerabilities via email.

File-Level Changes

Change	Details	Files
Define a concrete security policy section with updated vulnerability reporting contact information.	Replace the placeholder vulnerability reporting instructions with a formal 'Security Policy' section Add a 'Reporting a Vulnerability' subsection describing how to report issues Specify dev@wevm.dev as the official contact email for security reports using a mailto link	SECURITY.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the SECURITY.md file to provide clearer and more direct instructions for reporting vulnerabilities. The changes involve updating the contact email to a specific address and improving the document's structure with appropriate markdown headings, ensuring that users can easily identify the correct channel for security concerns.

Highlights

• Contact Email Update: The generic placeholder email your-security-email@example.com for reporting vulnerabilities has been replaced with the specific contact dev@wevm.dev.
• Document Structure Improvement: The SECURITY.md file now includes proper markdown headings, # Security Policy and ## Reporting a Vulnerability, to enhance readability and organization.
• Reporting Process Simplification: Detailed text regarding expected response times for vulnerability reports has been removed, making the reporting instructions more concise.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[sourcery-ai]

Hey - I've left some high level feedback:

• It looks like # Security Policy may already exist earlier in SECURITY.md from the default GitHub template; consider avoiding a duplicate top-level heading and just updating the existing “Reporting a Vulnerability” section.
• The revision drops the prior guidance about expected response times and update cadence for reports; if that information is still applicable, consider keeping a brief note so reporters know what to expect after contacting dev@wevm.dev.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- It looks like `# Security Policy` may already exist earlier in `SECURITY.md` from the default GitHub template; consider avoiding a duplicate top-level heading and just updating the existing “Reporting a Vulnerability” section.
- The revision drops the prior guidance about expected response times and update cadence for reports; if that information is still applicable, consider keeping a brief note so reporters know what to expect after contacting `dev@wevm.dev`.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request updates the contact information for reporting security vulnerabilities. However, the current change introduces duplicate headers and removes some useful information from the SECURITY.md file. I've provided a suggestion to correct the formatting and restore the helpful details about response expectations, which will improve clarity for anyone reporting a vulnerability. Please also note the recommendation to remove a now-redundant placeholder line.