enssdk
The foundational ENS development library
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Package is an intentional name reservation placeholder for the ENSNode project by NameHash Labs; tiny payload and missing metadata are expected for this use case. | ai | |
| dependencies | unvetted-dep:caip | AI (dependencies): caip is the well-known Chain Agnostic Improvement Proposals library, a standard dependency in blockchain/ENS tooling. No security concerns. | ai | |
| dependencies | unvetted-dep:@ensdomains/address-encoder | AI (dependencies): @ensdomains/address-encoder is the official ENS address encoder library, a standard and expected dependency for ENS SDK packages. | ai | |
| provenance | no-provenance | AI (provenance): enssdk is a legitimate ENS ecosystem library from the namehash/ensnode org; lack of provenance is common and not a risk indicator here. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.15.1 | 3 / 8 | |
| 1.15.0 | 3 / 8 | |
| 1.14.0 | 3 / 8 | |
| 1.13.1 | 3 / 8 | |
| 1.12.0 | 3 / 8 | |
| 1.11.1 | 3 / 8 | |
| 1.11.0 | 3 / 8 | |
| 1.10.1 | 3 / 8 | |
| 1.10.0 | 3 / 8 | |
| 0.0.1 | 0 / 0 |
v1.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lightwalker_eth.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lightwalker_eth.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lightwalker_eth.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lightwalker_eth.
[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.