fix: update

[Dargon789]

Summary by Sourcery

Enhance ID generation security, bump happy-dom dependency to 20.0.2, and introduce a SECURITY.md policy document

Enhancements:

• Switch to crypto.getRandomValues for secure random ID generation

Build:

• Upgrade happy-dom to 20.0.2 in dapp-client and wdk packages

Documentation:

• Add SECURITY.md outlining 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.

[sourcery-ai]

Reviewer's Guide

Implements cryptographically secure ID generation, upgrades happy-dom to v20.0.2 in wallet packages, and adds a SECURITY.md with the project’s security support policy and reporting process.

Class diagram for updated DappTransport.generateId() method

classDiagram
class DappTransport {
  +generateId(): string
  - Old: Math.random()
  + New: window.crypto.getRandomValues(array: Uint32Array)
}
DappTransport : +generateId() uses window.crypto.getRandomValues

Loading

File-Level Changes

Change	Details	Files
Switch ID generation from Math.random to crypto.getRandomValues	Removed Math.random-based substring generation Initialized a Uint32Array and populated it with crypto.getRandomValues Converted the random value to base-36 and composed the ID string	packages/wallet/dapp-client/src/DappTransport.ts
Bump happy-dom dependency to v20.0.2	Updated happy-dom version in dapp-client’s package.json Updated happy-dom version in wdk’s package.json	packages/wallet/dapp-client/package.json packages/wallet/wdk/package.json
Add SECURITY.md with support and reporting guidelines	Created SECURITY.md outlining supported versions table Defined the vulnerability reporting email and expected response timeline	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.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
sequence-js-web	Ready	Preview	Comment	Nov 14, 2025 9:09am
sequence.js	Ready	Preview	Comment	Nov 14, 2025 9:09am

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
sequence-js-docs	Skipped			Nov 14, 2025 9:09am

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

[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 focuses on bolstering the project's security posture by introducing a formal security policy and enhancing the cryptographic strength of ID generation. It also includes routine dependency updates to keep the project's libraries current and secure.

Highlights

• Security Policy: A new SECURITY.md file has been added to the repository, outlining supported versions and the process for reporting vulnerabilities.
• Enhanced Randomness: The generateId method in DappTransport.ts has been updated to use window.crypto.getRandomValues for cryptographically secure ID generation, replacing the less secure Math.random().
• Dependency Updates: The happy-dom dependency has been upgraded from version 17.2.2 to 20.0.2 in both dapp-client and wdk packages. The pnpm-lock.yaml file has been updated to reflect this and other related dependency changes, including @types/node and the removal of webidl-conversions.

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 - here's some feedback:

• Add a fallback for environments without window.crypto (e.g. Node) so generateId still works universally.
• Consider normalizing the random string to a fixed length (e.g. pad or truncate) to maintain consistent ID formats.
• After bumping happy-dom in package.json, regenerate the pnpm-lock.yaml to keep your lockfile in sync.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Add a fallback for environments without window.crypto (e.g. Node) so generateId still works universally.
- Consider normalizing the random string to a fixed length (e.g. pad or truncate) to maintain consistent ID formats.
- After bumping happy-dom in package.json, regenerate the pnpm-lock.yaml to keep your lockfile in sync.

## Individual Comments

### Comment 1
<location> `SECURITY.md:3-8` </location>
<code_context>
+
+## Supported Versions
+
+Use this section to tell people about which versions of your project are
+currently being supported with security updates.
+
+| Version | Supported          |
</code_context>

<issue_to_address>
**suggestion:** Consider removing or rephrasing the template instruction about supported versions.

The sentence appears to be a template instruction and should be removed or rewritten for end users.

```suggestion
## Supported Versions

The following table lists which versions of this project currently receive security updates.

| Version | Supported          |
```
</issue_to_address>

---

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 enhances security by using crypto.getRandomValues for ID generation, bumps the happy-dom dependency, and adds a SECURITY.md file. The changes are positive, particularly the move to a cryptographically secure random number generator. I've provided a couple of suggestions for improvement: one to refine the new ID generation logic to ensure a fixed length and higher entropy, and another to populate the placeholder content in the new SECURITY.md file.