@sentry/utils
Utilities for all Sentry JavaScript SDKs
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Diff is cross-major (v8→v7); v7 and v8 have different architectures. Large file count difference is a structural artifact, not injected code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is due to cross-major comparison (v8.55.0 vs v7.120.4). @sentry/utils v7 legitimately includes more utilities than the v8 equivalent. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @sentry/types is a first-party Sentry dependency pinned to the same version (7.120.4); standard v7 SDK architecture where types is a separate package. | ai | |
| source-diff | obfuscated-file:build/esm/index.js | AI (source-diff): Long lines are barrel re-exports of many symbols from @sentry/core, not obfuscation. This is the standard v8 SDK architecture for @sentry/utils. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop reflects v8 architectural change: utility code moved to @sentry/core; @sentry/utils is now a thin re-export layer. | ai | |
| source-diff | obfuscated-file:build/types-ts3.8/index.d.ts | AI (source-diff): Long lines are TypeScript declaration re-exports from @sentry/core. Standard pattern for Sentry v8 SDK compatibility shim. | ai | |
| source-diff | obfuscated-file:build/types/index.d.ts | AI (source-diff): Long lines are TypeScript declaration re-exports from @sentry/core. Standard pattern for Sentry v8 SDK compatibility shim. | ai |
Versions (showing 51 of 413)
| Version | Deps | Published |
|---|---|---|
| 8.55.2 | 1 / 0 | |
| 8.55.1 | 1 / 0 | |
| 8.55.0 | 1 / 0 | |
| 8.54.0 | 1 / 0 | |
| 8.53.0 | 1 / 0 | |
| 8.52.1 | 1 / 0 | |
| 8.52.0 | 1 / 0 | |
| 8.51.0 | 1 / 0 | |
| 8.50.0 | 1 / 0 | |
| 8.49.0 | 1 / 0 | |
| 8.48.0 | 1 / 0 | |
| 8.47.0 | 1 / 0 | |
| 8.46.0 | 1 / 0 | |
| 8.45.1 | 1 / 0 | |
| 8.45.0 | 1 / 0 | |
| 8.44.0 | 1 / 0 | |
| 8.43.0 | 1 / 0 | |
| 8.42.0 | 1 / 0 | |
| 8.41.0 | 2 / 0 | |
| 8.40.0 | 2 / 0 | |
| 8.39.0 | 1 / 2 | |
| 8.38.0 | 1 / 2 | |
| 8.37.1 | 1 / 2 | |
| 8.37.0 | 1 / 2 | |
| 8.36.0 | 1 / 2 | |
| 8.35.0 | 1 / 2 | |
| 8.34.0 | 1 / 2 | |
| 8.33.1 | 1 / 2 | |
| 8.33.0 | 1 / 2 | |
| 8.32.0 | 1 / 2 | |
| 8.31.0 | 1 / 2 | |
| 8.30.0 | 1 / 2 | |
| 8.29.0 | 1 / 2 | |
| 8.28.0 | 1 / 2 | |
| 8.27.0 | 1 / 2 | |
| 8.26.0 | 1 / 2 | |
| 8.25.0 | 1 / 2 | |
| 8.24.0 | 1 / 2 | |
| 8.23.0 | 1 / 2 | |
| 8.22.0 | 1 / 2 | |
| 8.21.0 | 1 / 2 | |
| 8.20.0 | 1 / 2 | |
| 8.19.0 | 1 / 2 | |
| 8.18.0 | 1 / 2 | |
| 8.17.0 | 1 / 2 | |
| 8.16.0 | 1 / 2 | |
| 8.15.0 | 1 / 2 | |
| 8.14.0 | 1 / 2 | |
| 8.13.0 | 1 / 2 | |
| 8.12.0 | 1 / 2 | |
| 8.11.0 | 1 / 2 |
v8.55.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.55.1
4 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.
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.
v8.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.52.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.