docs(examples): adds new example to repo

[emnul]

Summary

Creates a new example in the repository that demonstrates how to use the Ethereum Attestation Service with a Defender Relay Signer

[changeset-bot]

⚠️ No Changeset found

Latest commit: fdee62e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@ethereum-attestation-service/eas-sdk@2.7.0	Transitive: environment, eval, filesystem, network, shell, unsafe	+61	97.4 MB	lbeder
npm/@openzeppelin/defender-sdk@1.15.2	Transitive: environment, filesystem, network, shell	+28	8.55 MB	collins-oz
npm/ethers@6.13.4	Transitive: environment, network	+5	15.6 MB	ricmoo

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
High CVE	npm/ws@7.4.6	CVE: GHSA-3h5v-q93c-6h6q ws affected by a DoS when handling a request with many HTTP headers (HIGH) Affected versions: >= 7.0.0, < 7.5.10 Patched version: 7.5.10	examples/eas-relayer-signer/package.json	🚫
AI-detected potential code anomaly	npm/undici@5.28.4	Notes: The code appears to be a WebAssembly (WASM) module implementing HTTP parsing functionality. The code contains suspicious elements such as ability to handle HTTP headers, message bodies, and chunk extensions. While it may be legitimate parser code, the obfuscated nature and presence of low-level binary operations warrants careful review due to potential for misuse in HTTP request/response manipulation or header injection attacks. Confidence: 1.00 Severity: 0.60	examples/eas-relayer-signer/package.json	🚫
AI-detected potential code anomaly	npm/undici@5.28.4	Notes: The code appears to be a WebAssembly (WASM) module implementing HTTP parsing functionality. The code contains suspicious elements such as ability to handle HTTP headers, message bodies, and chunk extensions. While it may be legitimate parser code, the obfuscated nature and presence of low-level binary operations warrants careful review due to potential for misuse in HTTP request/response manipulation or header injection attacks. Confidence: 1.00 Severity: 0.60	examples/eas-relayer-signer/package.json	🚫

View full report↗︎

Next steps

What is a CVE?

Contains a high severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What is an AI-detected potential code anomaly?

AI has identified unusual behaviors that may pose a security risk.

An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/ws@7.4.6
• @SocketSecurity ignore npm/undici@5.28.4

[RaphaelMagnux]

Hello!

I see that for onchain attestation there is not type 🥲

Any idea about what would be?

[emnul]

@RaphaelMagnux Hi the type seems to be AttestationRequest found here

[RaphaelMagnux]

Thank you, I already found a solution, instead use EAS SDK, I´m calling directly to EAS.sol smart contract with ethers and OZ Relayer, it works.

Thanksssss