@aave/react
The official React bindings for the Aave Protocol
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation is a documented supply-chain improvement, not a compromise. | ai | |
| source-diff | obfuscated-file:dist/viem/index.cjs | AI (source-diff): Standard minified bundle output; sample shows normal React hooks and Aave SDK logic with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/viem/index.js | AI (source-diff): Standard minified ESM bundle; sample shows normal Aave SDK imports and viem integration, no malicious patterns. | ai | |
| provenance | no-provenance | AI (provenance): Established Aave SDK package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 6.1.0 | 5 / 14 | |
| 4.1.1 | 5 / 14 | |
| 4.1.0 | 5 / 14 | |
| 4.0.4 | 5 / 14 | |
| 4.0.3 | 5 / 14 | |
| 4.0.2 | 5 / 14 | |
| 4.0.1 | 5 / 14 | |
| 4.0.0 | 5 / 14 | |
| 0.8.3 | 4 / 13 | |
| 0.8.2 | 4 / 13 | |
| 0.8.1 | 4 / 13 | |
| 0.8.0 | 4 / 13 | |
| 0.7.1 | 4 / 13 | |
| 0.6.1 | 4 / 13 | |
| 0.6.0 | 4 / 13 | |
| 0.5.0 | 4 / 12 | |
| 0.4.0 | 4 / 12 | |
| 0.3.1 | 4 / 12 | |
| 0.3.0 | 4 / 12 | |
| 0.2.0 | 4 / 12 | |
| 0.1.0 | 4 / 12 |
v6.1.0
4 findingsThis version was published by a different npm account than previous versions on 2026-06-01. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.