@sentry/bundler-plugin-core
Sentry Bundler Plugin Core
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Sentry monorepo package; README link pattern is standard for their ecosystem, not a link farm. | ai | |
| dependencies | unvetted-dep:@sentry/babel-plugin-component-annotate | AI (dependencies): First-party Sentry package co-released at the same version; stable dependency pattern across versions. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.3.0 | 7 / 11 | |
| 5.2.1 | 7 / 11 | |
| 5.2.0 | 7 / 11 | |
| 5.1.1 | 7 / 14 | |
| 5.1.0 | 7 / 14 | |
| 5.0.0 | 7 / 14 | |
| 4.9.1 | 8 / 20 | |
| 4.9.0 | 8 / 20 | |
| 4.8.0 | 8 / 20 | |
| 4.7.0 | 8 / 20 | |
| 4.6.2 | 8 / 20 | |
| 4.6.1 | 8 / 20 |
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.