@sentry/node
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Dep swap is an intra-org rename (@sentry-internal/server-utils → @sentry/server-utils); not an external supply-chain addition. | ai | |
| dependencies | unvetted-dep:@sentry-internal/server-utils | AI (dependencies): Sentry-internal monorepo package pinned to exact matching version; consistent with routine SDK refactoring. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Diff is cross-major-version (v8 vs v10); file count difference is expected. | ai | |
| source-diff | obfuscated-file:build/cjs/integrations/anr/index.js | AI (source-diff): Base64 worker script for ANR detection; standard Sentry pattern across versions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): @sentry/node has 698 versions and 19.1M weekly downloads; it publishes continuously. The dormancy finding is a data artifact from comparing against a specific prior approved version. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Sentry regularly rotates team members on npm; sentry-bot is the stable publishing account. Maintainer churn is normal for this org and not a takeover signal. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): @sentry/node is the official Sentry Node SDK under the @sentry scope — not a typosquat of 'zod'. Levenshtein distance match is a false positive for this scoped package. | ai | |
| provenance | no-provenance | AI (provenance): sentry-bot is a well-established publisher with 3865 approved packages. Lack of provenance attestation is acceptable for this trusted publisher. | ai | |
| phantom-deps | phantom-dep:import-in-the-middle | AI (phantom-deps): import-in-the-middle is a legitimate runtime dependency declared in package.json, used by Sentry for ESM module interception. Not a phantom dep concern. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 10.58.0 | 10 / 1 | |
| 10.57.0 | 10 / 1 | |
| 10.56.0 | 10 / 1 | |
| 10.55.0 | 9 / 1 | |
| 10.54.0 | 9 / 1 | |
| 10.53.1 | 29 / 1 | |
| 10.53.0 | 29 / 1 | |
| 10.52.0 | 29 / 1 | |
| 10.51.0 | 31 / 1 | |
| 10.50.0 | 31 / 1 | |
| 10.49.0 | 32 / 1 | |
| 10.48.0 | 34 / 1 | |
| 10.47.0 | 35 / 1 | |
| 10.46.0 | 35 / 1 | |
| 10.45.0 | 35 / 1 | |
| 10.44.0 | 35 / 1 | |
| 10.43.0 | 35 / 1 | |
| 10.42.0 | 35 / 1 | |
| 10.41.0 | 35 / 1 | |
| 10.40.0 | 35 / 1 | |
| 10.39.0 | 35 / 1 | |
| 10.38.0 | 35 / 1 | |
| 10.37.0 | 35 / 1 | |
| 10.36.0 | 35 / 1 | |
| 10.35.0 | 35 / 1 | |
| 10.34.0 | 35 / 1 | |
| 10.33.0 | 35 / 1 | |
| 10.32.1 | 35 / 1 | |
| 10.32.0 | 35 / 1 | |
| 10.31.0 | 35 / 1 | |
| 10.30.0 | 35 / 1 | |
| 10.29.0 | 35 / 1 | |
| 10.28.0 | 35 / 1 | |
| 10.27.0 | 35 / 1 | |
| 10.10.0 | 35 / 1 | |
| 10.9.0 | 35 / 1 | |
| 10.8.0 | 35 / 1 | |
| 10.7.0 | 35 / 1 | |
| 10.6.0 | 35 / 1 | |
| 10.5.0 | 35 / 1 | |
| 10.4.0 | 35 / 1 | |
| 10.3.0 | 35 / 1 | |
| 10.2.0 | 35 / 1 | |
| 10.1.0 | 35 / 1 | |
| 10.0.0 | 35 / 1 | |
| 9.47.1 | 35 / 1 | |
| 9.47.0 | 35 / 1 | |
| 8.55.2 | 35 / 1 | |
| 8.55.1 | 35 / 1 |
v10.58.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.57.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.56.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.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.