@ensnode/ensnode-sdk
A utility library for interacting with ENSNode and ENS data
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/internal.d.cts | AI (source-diff): Bundler-generated TypeScript declaration file with long re-export lines; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/internal.d.ts | AI (source-diff): Bundler-generated TypeScript declaration file with long re-export lines; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index.d.cts | AI (source-diff): dist/index.d.cts is a bundled TypeScript declaration file produced by tsup. Long lines are expected in concatenated .d.cts outputs; content is readable type declarations, not obfuscated code. | ai | |
| dependencies | unvetted-dep:caip | AI (dependencies): caip is a well-known Chain Agnostic Improvement Proposals library used throughout the Ethereum ecosystem; unvetted status reflects review gap, not risk. | ai | |
| dependencies | unvetted-dep:@ensdomains/address-encoder | AI (dependencies): @ensdomains/address-encoder is the official ENS address encoder maintained by ENS Labs; unvetted status reflects review gap, not risk. | ai | |
| phantom-deps | phantom-dep:@ensdomains/address-encoder | AI (phantom-deps): @ensdomains/address-encoder is a declared runtime dependency used in config/type contexts; phantom-dep flag is a stable false positive for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.15.1 | 6 / 6 | |
| 1.15.0 | 6 / 6 | |
| 1.14.0 | 6 / 6 | |
| 1.13.1 | 6 / 6 | |
| 1.13.0 | 6 / 6 | |
| 1.12.0 | 6 / 6 | |
| 1.11.1 | 6 / 6 | |
| 1.11.0 | 6 / 6 | |
| 1.10.1 | 6 / 6 | |
| 1.10.0 | 6 / 6 | |
| 1.9.0 | 6 / 6 | |
| 1.8.1 | 6 / 6 | |
| 1.5.0 | 7 / 6 | |
| 1.3.0 | 7 / 6 | |
| 1.2.0 | 7 / 6 | |
| 1.1.0 | 7 / 6 | |
| 1.0.3 | 7 / 6 | |
| 1.0.2 | 7 / 6 | |
| 1.0.1 | 7 / 6 | |
| 1.0.0 | 7 / 6 |
v1.15.1
3 findingsNewly 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
3 findingsNewly 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
3 findingsNewly 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
3 findingsThis version was published by a different npm account than previous versions on 2026-03-24. 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
3 findingsThis version was published by a different npm account than previous versions on 2026-01-14. 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
3 findingsThis version was published by a different npm account than previous versions on 2025-12-10. 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.