@sentry/browser
Official Sentry SDK for browsers
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
Versions (showing 100 of 506)
| Version | Deps | Published |
|---|---|---|
| 9.10.1 | 5 / 2 | |
| 9.10.0 | 5 / 2 | |
| 9.9.0 | 5 / 2 | |
| 9.8.0 | 5 / 2 | |
| 9.7.0 | 5 / 2 | |
| 9.6.1 | 5 / 2 | |
| 9.6.0 | 5 / 2 | |
| 9.5.0 | 5 / 2 | |
| 9.4.0 | 5 / 2 | |
| 9.3.0 | 5 / 2 | |
| 9.2.0 | 5 / 2 | |
| 9.1.0 | 5 / 2 | |
| 9.0.1 | 5 / 2 | |
| 9.0.0 | 5 / 2 | |
| 8.55.2 | 5 / 2 | |
| 8.55.1 | 5 / 2 | |
| 8.55.0 | 5 / 2 | |
| 8.54.0 | 5 / 2 | |
| 8.53.0 | 5 / 2 | |
| 8.52.1 | 5 / 2 | |
| 8.52.0 | 5 / 2 | |
| 8.51.0 | 5 / 2 | |
| 8.50.0 | 5 / 2 | |
| 8.49.0 | 5 / 2 | |
| 8.48.0 | 5 / 2 | |
| 8.47.0 | 5 / 2 | |
| 8.46.0 | 5 / 2 | |
| 8.45.1 | 5 / 2 | |
| 8.45.0 | 5 / 2 | |
| 8.44.0 | 5 / 2 | |
| 8.43.0 | 5 / 2 | |
| 8.42.0 | 5 / 2 | |
| 8.41.0 | 6 / 2 | |
| 8.40.0 | 6 / 2 | |
| 8.39.0 | 7 / 2 | |
| 8.38.0 | 7 / 2 | |
| 8.37.1 | 7 / 2 | |
| 8.37.0 | 7 / 2 | |
| 8.36.0 | 7 / 2 | |
| 8.35.0 | 7 / 2 | |
| 8.34.0 | 7 / 2 | |
| 8.33.1 | 7 / 2 | |
| 8.33.0 | 7 / 2 | |
| 7.120.4 | 8 / 22 | |
| 7.120.3 | 8 / 22 | |
| 7.120.2 | 8 / 22 | |
| 7.120.1 | 8 / 22 | |
| 7.120.0 | 8 / 22 | |
| 7.119.2 | 8 / 22 | |
| 7.119.1 | 8 / 22 | |
| 7.111.0 | 7 / 22 | |
| 7.110.1 | 7 / 22 | |
| 7.110.0 | 7 / 22 | |
| 7.109.0 | 7 / 22 | |
| 7.108.0 | 7 / 22 | |
| 7.107.0 | 7 / 22 | |
| 7.106.1 | 7 / 22 | |
| 7.106.0 | 7 / 22 | |
| 7.105.0 | 7 / 22 | |
| 7.104.0 | 7 / 22 | |
| 7.103.0 | 7 / 22 | |
| 7.102.1 | 7 / 22 | |
| 7.102.0 | 7 / 22 | |
| 7.101.1 | 7 / 22 | |
| 7.101.0 | 7 / 22 | |
| 7.100.1 | 7 / 22 | |
| 7.100.0 | 7 / 22 | |
| 7.99.0 | 7 / 22 | |
| 7.98.0 | 7 / 22 | |
| 7.97.0 | 7 / 22 | |
| 7.96.0 | 7 / 22 | |
| 7.95.0 | 7 / 22 | |
| 7.94.1 | 7 / 22 | |
| 7.93.0 | 6 / 21 | |
| 7.92.0 | 6 / 21 | |
| 7.91.0 | 6 / 21 | |
| 7.90.0 | 6 / 21 | |
| 7.89.0 | 6 / 21 | |
| 7.88.0 | 6 / 21 | |
| 7.87.0 | 6 / 21 | |
| 7.86.0 | 6 / 21 | |
| 7.85.0 | 6 / 21 | |
| 7.84.0 | 5 / 21 | |
| 7.83.0 | 5 / 21 | |
| 7.82.0 | 5 / 21 | |
| 7.81.1 | 5 / 21 | |
| 7.81.0 | 5 / 21 | |
| 7.80.1 | 5 / 21 | |
| 7.80.0 | 5 / 21 | |
| 7.79.0 | 5 / 21 | |
| 7.78.0 | 5 / 21 | |
| 7.77.0 | 5 / 21 | |
| 7.76.0 | 5 / 21 | |
| 7.75.1 | 5 / 21 | |
| 7.75.0 | 5 / 21 | |
| 7.74.1 | 6 / 21 | |
| 7.74.0 | 6 / 21 | |
| 7.73.0 | 6 / 21 | |
| 7.72.0 | 6 / 21 | |
| 7.71.0 | 6 / 21 |
v9.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.55.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.55.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.52.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.120.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.120.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.120.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.120.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.120.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.119.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.119.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.