build(deps): bump the npm_and_yarn group across 1 directory with 2 updates

[jddunn]

📋 Summary

Describe the change and why it is needed.

🧾 Auto Summary

• Pending CI update

🔗 Related Issues

Closes #

📝 Type of Change

• ✨ Feature
• 🐛 Fix
• 💥 Breaking Change
• 📚 Docs
• 🧪 Tests
• 🔧 Build / CI
• ♻️ Refactor
• ⚡ Performance
• 🧹 Chore
• 📦 Dependencies

🧪 Testing

Describe tests added/updated and manual verification steps.

✅ Checklist

• Code follows style (lint passes)
• Added/updated tests
• Updated docs / README (if user-facing change)
• No new ESLint warnings
• Changes are backward compatible (or noted as breaking)

💥 Breaking Changes

If breaking, describe impact and migration path.

📸 Screenshots / Logs (optional)

📌 Additional Notes

🚀 Post-Merge Actions

• Publish package (if needed)
• Announce / release notes

Summary by Sourcery

Update esbuild dependency to v0.25.0 and introduce a SECURITY.md with supported versions and vulnerability reporting guidelines.

Enhancements:

• Bump esbuild from v0.21.5 to v0.25.0

Documentation:

• Add SECURITY.md outlining supported versions and vulnerability reporting process

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[sourcery-ai]

Reviewer's Guide

This PR updates the project’s build dependency by bumping esbuild from 0.21.5 to 0.25.0 (with a regenerated pnpm lockfile) and adds a SECURITY.md to define supported versions and vulnerability reporting procedures.

File-Level Changes

Change	Details	Files
Bump esbuild dependency and regenerate lockfile	Updated esbuild version range in package.json Regenerated pnpm-lock.yaml to lock the updated version	package.json pnpm-lock.yaml
Add project security policy document	Created SECURITY.md with supported versions table Outlined vulnerability reporting guidelines and timelines	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.

[github-actions]

🏷️ Auto-labeling complete

Applied: documentation, area: docs, area: build, dependencies, size: S, security

[Copilot]

Pull Request Overview

This PR adds a security policy document and updates a build dependency. The purpose appears to be establishing security guidelines for the project and keeping development dependencies current.

• Added a SECURITY.md file with vulnerability reporting guidelines and supported version information
• Updated esbuild dependency from version ^0.21.5 to ^0.25.0

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 3 comments.

File	Description
SECURITY.md	Adds new security policy template with placeholder content for vulnerability reporting
package.json	Updates esbuild development dependency to newer version

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The security policy contains placeholder text that should be replaced with actual project-specific information about supported versions and vulnerability reporting procedures.

[Copilot]

The version numbers in the supported versions table appear to be placeholder examples and should be updated to reflect the actual versions of this project.

Suggested change

	| 5.1.x | :white_check_mark: |
	| 5.0.x | :x: |
	| 4.0.x | :white_check_mark: |
	| < 4.0 | :x: |
	| 1.2.0 | :white_check_mark: |
	| 1.1.0 | :white_check_mark: |
	| 1.0.0 | :x: |
	| < 1.0.0 | :x: |

[Copilot]

The vulnerability reporting section contains placeholder instructions and should be replaced with specific contact information and procedures for this project.

Suggested change

	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.
	To report a security vulnerability, please email us at [security@example.com](mailto:security@example.com) with details of the issue.
	We aim to acknowledge all reports within 2 business days and provide a status update within 7 business days.
	After triage, we will keep you informed of our progress and may request additional information if needed. If the vulnerability is accepted, we will work with you on disclosure timing and credit. If declined, we will provide a clear explanation.

[github-actions]

✨ Auto-formatted code with Prettier

I've automatically formatted the code to match the project's style guidelines. The changes have been pushed to this PR.

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

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.}