@ensnode/ensdb-sdk
SDK for interacting with data in ENSDb
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/index-1D8_3_7g.d.ts | AI (source-diff): Generated .d.ts bundle from tsup; long lines are normal for bundled TypeScript declarations, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-DdrIzPaZ.d.ts | AI (source-diff): Bundled .d.ts type declaration from tsup; long lines are normal for generated type bundles, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-CVAtPcO6.d.ts | AI (source-diff): Bundled .d.ts type declaration file from tsup; long lines are expected in generated type bundles, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-C0lByZGy.d.ts | AI (source-diff): Bundled .d.ts type declaration file from tsup; long lines are normal for generated TypeScript declarations, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-DHRbRciU.d.ts | AI (source-diff): Long-line .d.ts files are bundled TypeScript type declarations generated by tsup, not obfuscated executable code. Content is clearly readable type definitions for ponder/drizzle-orm schemas. | ai | |
| source-diff | obfuscated-file:dist/index-DN0SGSyd.d.ts | AI (source-diff): This is a generated TypeScript declaration file (.d.ts) from tsup build tooling. Long lines in .d.ts files are normal artifacts of type generation, not obfuscation. Stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): ENSNode monorepo packages consistently lack Sigstore provenance; this is a stable characteristic of the publisher's release pipeline, not a risk indicator. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.15.1 | 4 / 8 | |
| 1.15.0 | 4 / 8 | |
| 1.14.0 | 4 / 8 | |
| 1.13.1 | 4 / 8 | |
| 1.13.0 | 4 / 8 | |
| 1.12.0 | 4 / 8 | |
| 1.11.1 | 4 / 8 | |
| 1.11.0 | 4 / 8 | |
| 1.10.1 | 4 / 8 | |
| 1.10.0 | 4 / 8 | |
| 1.9.0 | 0 / 9 | |
| 1.8.1 | 0 / 9 | |
| 1.8.0 | 0 / 9 |
v1.15.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[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
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.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.
v1.8.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.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.