@sentry/node-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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Sentry publishes many packages without Sigstore provenance; this is consistent across their entire SDK suite and not a risk indicator for this publisher. | ai | |
| source-diff | encoded-string-file:build/cjs/integrations/anr/index.js | AI (source-diff): Base64 string is Sentry's embedded ANR worker thread script, a documented pattern in the Sentry Node SDK. Decoded content is standard Sentry SDK code with no malicious payload. | ai | |
| source-diff | encoded-string-file:build/esm/integrations/anr/index.js | AI (source-diff): Same as CJS counterpart — base64-encoded Sentry ANR worker script, benign and documented pattern. | ai | |
| source-diff | encoded-string-file:build/esm/integrations/local-variables/local-variables-async.js | AI (source-diff): Same as CJS counterpart — base64-encoded Sentry local-variables worker script, benign and documented pattern. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): @sentry/node-core is a newer split package from @sentry/node; version gaps reflect SDK release cadence, not account takeover. Publisher sentry-bot has strong track record. | ai | |
| source-diff | encoded-string-file:build/cjs/integrations/local-variables/local-variables-async.js | AI (source-diff): Base64 string is Sentry's embedded local-variables worker thread script. Decoded content is standard Sentry SDK inspector/worker code. | ai | |
| dependencies | unvetted-dep:@sentry/opentelemetry | AI (dependencies): @sentry/opentelemetry is a first-party Sentry monorepo package always released in lockstep with @sentry/node-core; not a third-party risk. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 10.55.0 | 3 / 7 | |
| 10.54.0 | 3 / 7 | |
| 10.53.1 | 3 / 7 | |
| 10.53.0 | 3 / 7 | |
| 10.52.0 | 3 / 7 | |
| 10.51.0 | 3 / 7 | |
| 10.50.0 | 3 / 7 | |
| 10.49.0 | 3 / 7 | |
| 10.48.0 | 3 / 9 | |
| 10.47.0 | 3 / 9 | |
| 10.46.0 | 3 / 8 | |
| 10.45.0 | 3 / 8 | |
| 10.44.0 | 3 / 8 | |
| 10.43.0 | 3 / 8 | |
| 10.42.0 | 3 / 8 | |
| 10.41.0 | 3 / 8 | |
| 10.40.0 | 3 / 8 | |
| 10.39.0 | 4 / 9 | |
| 10.38.0 | 4 / 9 | |
| 10.37.0 | 4 / 9 | |
| 10.36.0 | 4 / 9 | |
| 10.35.0 | 4 / 9 | |
| 10.34.0 | 4 / 9 | |
| 10.33.0 | 4 / 9 | |
| 10.32.1 | 4 / 9 | |
| 10.32.0 | 4 / 9 | |
| 10.31.0 | 4 / 9 | |
| 10.30.0 | 4 / 9 | |
| 10.29.0 | 4 / 9 | |
| 10.28.0 | 4 / 9 | |
| 10.27.0 | 4 / 9 | |
| 10.10.0 | 3 / 8 | |
| 10.9.0 | 3 / 8 | |
| 10.8.0 | 3 / 8 | |
| 10.7.0 | 3 / 8 | |
| 10.6.0 | 3 / 8 | |
| 10.5.0 | 3 / 8 | |
| 10.4.0 | 3 / 8 | |
| 10.3.0 | 3 / 8 | |
| 10.2.0 | 3 / 8 | |
| 10.1.0 | 3 / 8 | |
| 10.0.0 | 3 / 8 | |
| 9.47.1 | 3 / 8 | |
| 9.47.0 | 3 / 8 |
v10.55.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.54.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.53.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.53.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.52.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.51.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.50.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.49.0
5 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.48.0
5 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.32.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.47.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.