fix: Potential fix for code scanning alert no. 84: Insecure randomness #73

[Dargon789]

Summary by Sourcery

Address code scanning alert for insecure randomness by upgrading the happy-dom dependency and introduce a security policy document.

Bug Fixes:

• Upgrade happy-dom to v20.0.2 in dapp-client and wdk packages to mitigate insecure randomness

Documentation:

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

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

[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]

Reviewer's Guide

This PR addresses a code scanning alert by upgrading the test environment’s DOM simulation dependency to a newer, more secure version and introduces a SECURITY.md policy file to formalize vulnerability support and reporting procedures.

File-Level Changes

Change	Details	Files
Upgrade test DOM environment dependency	Bumped happy-dom version from 17.2.2 to 20.0.2 Updated pnpm lockfile to reflect the new happy-dom version	packages/wallet/dapp-client/package.json packages/wallet/wdk/package.json pnpm-lock.yaml
Add security policy documentation	Created SECURITY.md outlining supported versions Defined process for reporting and handling vulnerabilities	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 primarily focuses on enhancing the project's security posture by introducing a formal SECURITY.md document that details vulnerability reporting guidelines and supported versions. Additionally, it includes routine dependency maintenance, specifically upgrading the happy-dom library and updating several @types/node packages across the codebase. While the PR title references a "potential fix for code scanning alert no. 84: Insecure randomness", the provided changes do not directly show modifications to randomness-generating code but rather foundational security documentation and dependency updates.

Highlights

• Security Policy Addition: A new SECURITY.md file has been added to the repository, which formally outlines the project's security policy, specifies supported versions, and provides clear instructions for reporting vulnerabilities to the team.
• Dependency Updates: The happy-dom dependency has been upgraded from version 17.x.x to 20.x.x in the packages/wallet/dapp-client and packages/wallet/wdk modules, reflecting a significant update to this testing environment library.
• Type Definition and Lockfile Adjustments: Various @types/node packages have been updated to newer versions (e.g., 20.19.9 to 22.16.5) across the project's dependencies, and the pnpm-lock.yaml file has been comprehensively updated to reflect these changes, including the removal of webidl-conversions and the addition of new type definitions like @types/whatwg-mimetype.

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

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

[gemini-code-assist]

Code Review

This pull request effectively addresses the "Insecure randomness" security vulnerability by updating the happy-dom dependency across the affected packages. The changes in package.json files and the corresponding updates to pnpm-lock.yaml are correct and necessary to resolve the issue. The addition of a SECURITY.md file is also a commendable improvement, enhancing the project's security posture by providing clear guidelines for vulnerability reporting. I have one minor suggestion to improve the usability of the new security policy file.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
sequence-js-docs	Ready	Preview	Comment	Oct 25, 2025 7:02pm
sequence-js-web	Ready	Preview	Comment	Oct 25, 2025 7:02pm
sequence.js	Canceled			Oct 25, 2025 7:02pm