@sentry/minimal
Sentry minimal library that can be used in other packages
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Sentry migrated publishing from individual accounts to sentry-bot automation account; this is a documented org-level transition, not a compromise. Applies to all Sentry SDK packages. | ai |
Versions (showing 71 of 171)
| Version | Deps | Published |
|---|---|---|
| 5.16.0 | 3 / 7 | |
| 5.15.5 | 3 / 7 | |
| 5.15.4 | 3 / 7 | |
| 5.15.3 | 3 / 7 | |
| 5.15.2 | 3 / 7 | |
| 5.15.1 | 3 / 7 | |
| 5.15.0 | 3 / 7 | |
| 5.14.2 | 3 / 7 | |
| 5.14.1 | 3 / 7 | |
| 5.14.0 | 3 / 7 | |
| 5.13.2 | 3 / 7 | |
| 5.13.0 | 3 / 7 | |
| 5.12.5 | 3 / 7 | |
| 5.12.4 | 3 / 7 | |
| 5.12.0 | 3 / 7 | |
| 5.11.2 | 3 / 7 | |
| 5.11.1 | 3 / 7 | |
| 5.11.0 | 3 / 7 | |
| 5.10.2 | 3 / 7 | |
| 5.10.1 | 3 / 7 | |
| 5.10.0 | 3 / 7 | |
| 5.8.0 | 3 / 7 | |
| 5.7.1 | 3 / 7 | |
| 5.7.0 | 3 / 7 | |
| 5.6.1 | 3 / 7 | |
| 5.6.0 | 3 / 7 | |
| 5.5.0 | 3 / 7 | |
| 5.4.3 | 3 / 7 | |
| 5.4.2 | 3 / 7 | |
| 5.4.0 | 3 / 7 | |
| 5.3.0 | 3 / 7 | |
| 5.2.0 | 3 / 7 | |
| 5.1.2 | 3 / 7 | |
| 5.1.0 | 3 / 7 | |
| 5.0.8 | 3 / 7 | |
| 5.0.7 | 3 / 7 | |
| 5.0.6 | 3 / 7 | |
| 5.0.5 | 3 / 7 | |
| 5.0.3 | 3 / 7 | |
| 5.0.0 | 3 / 7 | |
| 4.6.5 | 3 / 7 | |
| 4.6.4 | 3 / 7 | |
| 4.6.3 | 3 / 7 | |
| 4.6.2 | 3 / 7 | |
| 4.6.1 | 3 / 7 | |
| 4.6.0 | 3 / 7 | |
| 4.5.4 | 3 / 7 | |
| 4.5.3 | 3 / 7 | |
| 4.5.2 | 3 / 7 | |
| 4.5.1 | 3 / 7 | |
| 4.5.0 | 3 / 7 | |
| 4.4.2 | 3 / 7 | |
| 4.4.1 | 3 / 7 | |
| 4.4.0 | 3 / 7 | |
| 4.3.4 | 3 / 7 | |
| 4.3.3 | 3 / 7 | |
| 4.3.2 | 2 / 7 | |
| 4.3.1 | 2 / 7 | |
| 4.3.0 | 2 / 7 | |
| 4.2.4 | 2 / 7 | |
| 4.2.3 | 2 / 7 | |
| 4.2.2 | 2 / 7 | |
| 4.2.1 | 2 / 7 | |
| 4.2.0 | 2 / 7 | |
| 4.1.1 | 2 / 7 | |
| 4.1.0 | 2 / 7 | |
| 4.0.6 | 2 / 7 | |
| 4.0.5 | 2 / 7 | |
| 4.0.1 | 2 / 7 | |
| 4.0.0 | 2 / 7 | |
| 0.5.4 | 2 / 7 |
v5.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.