Codesandbox

[Dargon789]

Summary by Sourcery

Add a wagmi-based demo app and integrate new security and CI workflows.

New Features:

• Introduce a new Vite-based React "wagmi-project" demonstrating wallet connection using wagmi and viem.

Enhancements:

• Record a new major version entry in the indexer service changelog.

Build:

• Add Vite, TypeScript, and React tooling configuration for the new wagmi demo project.

CI:

• Add a Fortify Application Security Testing GitHub Actions workflow for automated security scanning.
• Add an Azure Pipelines configuration to build the Node.js project on master branch pushes.

Deployment:

• Add CNAME and Codesandbox-related configuration files to support hosting and online sandboxing setups.

Documentation:

• Add SECURITY policy documentation and standardized GitHub issue templates for bugs, features, and custom issues.

Chores:

• Check in generated cache/map artifacts under v8-compile-cache-0 for preconstruct CLI.

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[snyk-io]

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

Status	Scan Engine	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

Adds a new wagmi-based Vite demo app and various project-scaffolding/configuration artifacts (security and issue templates, CI pipelines, Fortify SAST workflow), plus bumps the indexer service changelog to 2.0.0 with a placeholder entry.

Sequence diagram for wagmi wallet connect/disconnect flow

sequenceDiagram
  actor User
  participant App
  participant WagmiProvider
  participant useConnect
  participant useAccount
  participant useDisconnect

  User->>App: click connector button
  App->>useConnect: connect({ connector })
  useConnect->>WagmiProvider: connect
  WagmiProvider-->>useAccount: update account.status='connected'
  useAccount-->>App: account (status, addresses, chainId)
  App-->>User: render account info and Disconnect button

  User->>App: click Disconnect
  App->>useDisconnect: disconnect()
  useDisconnect->>WagmiProvider: disconnect
  WagmiProvider-->>useAccount: update account.status='disconnected'
  useAccount-->>App: account (status)
  App-->>User: hide Disconnect button, show Connect buttons

Loading

File-Level Changes

Change	Details	Files
Introduce a minimal wagmi + React Vite demo application under wagmi-project for wallet connection testing.	Bootstrap a Vite React TypeScript app with standard index.html, main entry, React root, and CSS baseline. Configure WagmiProvider with mainnet and sepolia chains, injected/WalletConnect/Coinbase connectors, and a shared QueryClient for react-query. Implement App component to display connection status, addresses, chainId, and allow connecting/disconnecting via available connectors. Add TypeScript, Vite, wagmi, viem, react-query, and build tooling configuration (tsconfig, tsconfig.node, vite.config, biome, .gitignore, .npmrc, vite env types, README).	wagmi-project/package.json wagmi-project/index.html wagmi-project/src/main.tsx wagmi-project/src/App.tsx wagmi-project/src/wagmi.ts wagmi-project/src/index.css wagmi-project/src/vite-env.d.ts wagmi-project/tsconfig.json wagmi-project/tsconfig.node.json wagmi-project/vite.config.ts wagmi-project/biome.json wagmi-project/.gitignore wagmi-project/.npmrc wagmi-project/README.md
Add security and issue management documentation/templates to standardize project processes.	Create SECURITY.md with placeholders for supported versions and vulnerability reporting process. Add GitHub issue templates for bug reports, feature requests, and a custom template.	SECURITY.md .github/ISSUE_TEMPLATE/bug_report.md .github/ISSUE_TEMPLATE/feature_request.md .github/ISSUE_TEMPLATE/custom.md
Add CI workflows for security scanning and basic Node.js builds.	Introduce a GitHub Actions workflow to run Fortify AST SAST scans on master pushes, PRs, schedules, and manual runs, configured to use Fortify on Demand secrets. Add an Azure Pipelines configuration that installs Node.js 10.x, runs npm install, and builds the project on master branch.	.github/workflows/fortify.yml azure-pipelines.yml
Update indexer service changelog to start 2.0.0 with a placeholder major-change entry.	Add 2.0.0 section with a 'Major Changes' header and placeholder 'changeset' entry above 1.10.14 in the indexer changelog.	packages/services/indexer/CHANGELOG.md
Check in various repository-level and tooling artifacts for Codesandbox and build caching.	Add Codesandbox tasks configuration and related repo-level metadata files. Introduce v8 compile cache map artifacts under v8-compile-cache-0 directory.	.codesandbox/tasks.json CNAME v8-compile-cache-0/x64/11.3.244.8-node.19/zSprojectzSsequence.jszSnode_moduleszS.pnpmzS@preconstruct+cli@2.8.7zSnode_moduleszS@preconstructzSclizSbin.js.MAP v8-compile-cache-0/x64/11.3.244.8-node.19/zSprojectzSworkspacezSnode_moduleszS.pnpmzS@preconstruct+cli@2.8.7zSnode_moduleszS@preconstructzSclizSbin.js.MAP

Possibly linked issues

• Feature/integration #17: They both describe adding the wagmi React project plus SECURITY.md, Azure Pipelines, and related placeholder/config files.

---

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]

Code Review

This pull request initializes a new Vite project using create-wagmi and adds various configuration files for CI/CD, CodeSandbox, and GitHub. The review feedback identifies several issues: the Azure pipeline uses an obsolete Node.js version and the wrong package manager, and environment-specific V8 cache artifacts were mistakenly committed. Additionally, the reviewer recommends pinning dependencies to specific versions instead of using the latest tag and suggests validating the WalletConnect project ID environment variable to ensure runtime stability.

[sourcery-ai]

Hey - I've found 2 issues, and left some high level feedback:

• It looks like various generated/cache artifacts (e.g. v8-compile-cache-0/...bin.js.MAP) and sandbox/infra files (e.g. .codesandbox/tasks.json, CNAME) are being committed; consider excluding these via .gitignore and keeping the PR focused on the actual app and workflow changes.
• The Azure pipeline is pinned to Node 10 (versionSpec: '10.x'), which is long out of support; aligning this to the runtime you actually use (and to what your app expects, e.g. Node 18+) would avoid surprises in the CI environment.
• In wagmi-project/src/wagmi.ts, walletConnect depends on import.meta.env.VITE_WC_PROJECT_ID; adding a simple runtime check or failing fast when this env var is missing would make misconfiguration easier to catch.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- It looks like various generated/cache artifacts (e.g. `v8-compile-cache-0/...bin.js.MAP`) and sandbox/infra files (e.g. `.codesandbox/tasks.json`, `CNAME`) are being committed; consider excluding these via `.gitignore` and keeping the PR focused on the actual app and workflow changes.
- The Azure pipeline is pinned to Node 10 (`versionSpec: '10.x'`), which is long out of support; aligning this to the runtime you actually use (and to what your app expects, e.g. Node 18+) would avoid surprises in the CI environment.
- In `wagmi-project/src/wagmi.ts`, `walletConnect` depends on `import.meta.env.VITE_WC_PROJECT_ID`; adding a simple runtime check or failing fast when this env var is missing would make misconfiguration easier to catch.

## Individual Comments

### Comment 1
<location path="wagmi-project/src/wagmi.ts" line_range="5-12" />
<code_context>
+  connectors: [
+    injected(),
+    coinbaseWallet(),
+    walletConnect({ projectId: import.meta.env.VITE_WC_PROJECT_ID }),
+  ],
+  transports: {
</code_context>
<issue_to_address>
**suggestion:** Handle missing or misconfigured `VITE_WC_PROJECT_ID` to avoid runtime failures.

If `VITE_WC_PROJECT_ID` is missing or empty, `walletConnect` will likely fail at runtime in a hard-to-debug way. Consider validating this value when creating the config (e.g., throw a clear error or skip the connector) so misconfiguration is surfaced early.

```suggestion
const wcProjectId = import.meta.env.VITE_WC_PROJECT_ID

if (!wcProjectId) {
  // Fail fast with a clear error instead of an opaque runtime failure inside walletConnect
  throw new Error(
    'VITE_WC_PROJECT_ID is not set. Please define it in your environment to enable WalletConnect.',
  )
}

export const config = createConfig({
  chains: [mainnet, sepolia],
  connectors: [
    injected(),
    coinbaseWallet(),
    walletConnect({ projectId: wcProjectId }),
  ],
  transports: {
```
</issue_to_address>

### Comment 2
<location path="wagmi-project/src/main.tsx" line_range="12" />
<code_context>
+
+import './index.css'
+
+globalThis.Buffer = Buffer
+
+const queryClient = new QueryClient()
</code_context>
<issue_to_address>
**suggestion (bug_risk):** Consider guarding or narrowing the global `Buffer` assignment to avoid unintended overrides.

Unconditionally setting `globalThis.Buffer` can clobber an existing implementation in some environments. Consider guarding it, e.g. `if (!globalThis.Buffer) globalThis.Buffer = Buffer`, so you only provide the polyfill when no `Buffer` is already defined.

```suggestion
if (!globalThis.Buffer) {
  globalThis.Buffer = Buffer
}
```
</issue_to_address>

Fix all in Cursor

---

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

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
sequence-js-docs	Canceled		May 22, 2026 10:31am
sequence-js-web	Canceled		May 22, 2026 10:31am
wagmi-project	Ready	Preview, Comment	May 22, 2026 10:31am