← Home

@sentry/rollup-plugin

npm Repository Homepage

Official Sentry Rollup plugin

12
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

sentry-bot

Keywords

Sentryrollup-pluginRollupbundlerplugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Sentry-bot is the official Sentry publisher; dormancy reflects a major version refactor, not account takeover. ai
source-diff source-size-tripled AI (source-diff): Size increase explained by dropping unplugin, adding magic-string, and switching build tooling to rolldown. ai
publish-pattern new-deps-added AI (publish-pattern): magic-string is a well-known, widely-used utility; addition is consistent with the refactor away from unplugin. ai
dependencies unvetted-dep:@sentry/bundler-plugin-core AI (dependencies): First-party Sentry monorepo package; same versioning cadence as this plugin, not a third-party risk. ai

Versions (showing 12 of 12)

Version Deps Published
5.3.0 2 / 9
5.2.1 2 / 9
5.2.0 2 / 9
5.1.1 2 / 12
5.1.0 2 / 12
5.0.0 2 / 12
4.9.1 2 / 17
4.9.0 2 / 17
4.8.0 2 / 17
4.7.0 2 / 17
4.6.2 2 / 17
4.6.1 2 / 17

v5.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.6.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.