@sentry/profiling-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 |
|---|---|---|---|---|
| install-scripts | install-script:install | AI (install-scripts): node-gyp rebuild is the standard install script for native Node.js addons; expected for a CPU profiler package that ships native bindings. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Precompiled .node binaries for multiple platforms/ABI versions are standard practice for native addon packages like a CPU profiler. Published by official Sentry bot. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in build check script to fall back to compiling from source — standard native addon pattern, not malicious. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in check-build.js loads the platform-specific prebuilt binary — standard native addon loading pattern, not arbitrary code execution. | ai | |
| provenance | no-provenance | AI (provenance): Sentry publishes via sentry-bot from the official getsentry/sentry-javascript monorepo; lack of Sigstore provenance is a known gap for this publisher, not a risk indicator. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 10.55.0 | 3 / 1 | |
| 10.54.0 | 3 / 1 | |
| 10.53.1 | 3 / 1 | |
| 10.53.0 | 3 / 1 | |
| 10.52.0 | 3 / 1 | |
| 10.51.0 | 3 / 1 | |
| 10.50.0 | 3 / 1 | |
| 10.49.0 | 3 / 1 | |
| 10.48.0 | 3 / 1 | |
| 10.47.0 | 3 / 1 | |
| 10.46.0 | 3 / 1 | |
| 10.45.0 | 3 / 1 | |
| 10.44.0 | 3 / 1 | |
| 10.43.0 | 3 / 1 | |
| 10.42.0 | 3 / 1 | |
| 10.41.0 | 3 / 1 | |
| 10.40.0 | 3 / 1 | |
| 10.39.0 | 3 / 1 | |
| 10.38.0 | 3 / 1 | |
| 10.37.0 | 3 / 1 | |
| 10.36.0 | 3 / 1 | |
| 10.35.0 | 3 / 1 | |
| 10.34.0 | 3 / 1 | |
| 10.33.0 | 3 / 1 | |
| 10.32.1 | 3 / 1 | |
| 10.32.0 | 3 / 1 | |
| 10.31.0 | 3 / 1 | |
| 10.30.0 | 3 / 1 | |
| 10.29.0 | 3 / 1 | |
| 10.28.0 | 3 / 1 | |
| 10.27.0 | 3 / 1 | |
| 10.26.0 | 3 / 1 | |
| 10.25.0 | 3 / 1 | |
| 10.24.0 | 3 / 1 | |
| 10.23.0 | 3 / 1 | |
| 10.22.0 | 3 / 1 | |
| 10.21.0 | 3 / 1 | |
| 10.20.0 | 3 / 1 | |
| 10.19.0 | 3 / 1 | |
| 10.18.0 | 3 / 1 | |
| 10.17.0 | 3 / 1 | |
| 10.16.0 | 3 / 1 | |
| 10.15.0 | 3 / 1 | |
| 10.14.0 | 3 / 1 | |
| 10.13.0 | 3 / 1 | |
| 10.12.0 | 3 / 1 | |
| 10.11.0 | 3 / 1 | |
| 10.10.0 | 3 / 1 | |
| 10.9.0 | 3 / 1 | |
| 10.8.0 | 3 / 1 | |
| 10.7.0 | 3 / 1 |
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.49.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.48.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.47.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.46.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.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.40.0
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.23.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.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.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.