Update examples to 1.28.0

[yosriady]

---

---

Note

Low Risk
Primarily dependency bumps and lockfile updates across example apps; the only logic change is in the Privy example’s identify flow, which affects analytics calls but not core app behavior.

Overview
Updates all example apps to use @formo/analytics ^1.28.0 (Privy to ^1.28.1), refreshing the corresponding lockfiles and picking up new optional Solana peer dependencies.

Adjusts the Privy example to auto-identify users from the Privy user profile via parsePrivyProperties on connect, and removes the manual “Identify User” button.

^{Written by Cursor Bugbot for commit d515a7f. This will update automatically on new commits. Configure here.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next@​15.5.3
	eslint-config-next@​15.5.3
	@​web3-onboard/​metamask@​2.2.1
	@​formo/​analytics@​1.27.0 ⏵ 1.28.0	-2		+1
	@​web3-onboard/​coinbase@​2.4.2
	@​web3-onboard/​react@​2.11.0
	@​types/​react@​18.3.28
	@​types/​node@​24.3.0 ⏵ 20.19.33
	@​web3-onboard/​injected-wallets@​2.11.3
	@​web3-onboard/​walletconnect@​2.6.3
	@​web3-onboard/​core@​2.24.1
	pino-pretty@​13.1.3
	@​tanstack/​react-query@​5.90.21
	@​eslint/​eslintrc@​2.1.4 ⏵ 3.3.4	+1
	eslint@​8.57.1 ⏵ 9.39.3	+1		+1	+46
	autoprefixer@​10.4.21 ⏵ 10.4.24	+1		-2

View full report

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: npm crypto-es PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard CVE: GHSA-mpj8-q39x-wq5h crypto-es PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard (CRITICAL) Affected versions: < 2.1.0 Patched version: 2.1.0 From: with-web3-onboard/package-lock.json → npm/@web3-onboard/react@2.11.0 → npm/@web3-onboard/core@2.24.1 → npm/crypto-es@1.2.7 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/crypto-es@1.2.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Critical CVE: Next.js is vulnerable to RCE in React flight protocol CVE: GHSA-9qr9-h5gf-34mp Next.js is vulnerable to RCE in React flight protocol (CRITICAL) Affected versions: >= 14.3.0-canary.77 < 15.0.5; >= 15.1.0-canary.0 < 15.1.9; >= 15.2.0-canary.0 < 15.2.6; >= 15.3.0-canary.0 < 15.3.6; >= 15.4.0-canary.0 < 15.4.8; >= 15.5.0-canary.0 < 15.5.7; >= 16.0.0-canary.0 < 16.0.7 Patched version: 15.5.7 From: with-web3-onboard/package-lock.json → npm/next@15.5.3 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/next@15.5.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Protestware or unwanted behavior: npm es5-ext Note: The script attempts to run a local post-install script, which could potentially contain malicious code. The error handling suggests that it is designed to fail silently, which is a common tactic in malicious scripts. From: with-web3-onboard/package-lock.json → npm/es5-ext@0.10.64 ℹ Read more on: This package | This alert | What is protestware? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Consider that consuming this package may come along with functionality unrelated to its primary purpose. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es5-ext@0.10.64. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}