@sentry-internal/node-cpu-profiler
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Sentry consolidated publishing to sentry-bot; removal of named maintainers is an org-level change, not a takeover indicator. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Infrequent binary releases are normal for this native binding; dormancy reflects release cadence, not account compromise. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is gated behind SENTRY_PROFILER_BINARY_PATH env var — an explicit user-controlled override for binary path, not arbitrary code execution. | ai | |
| install-scripts | install-script:install | AI (install-scripts): Install script runs check-build.js to verify/build native binaries — standard pattern for native Node.js addon packages from a trusted publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Sentry package not intended for general discovery; short README and no keywords are cosmetic, not security signals. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in install-time check-build.js to verify/build native binaries — expected for a native addon package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Bundled .node binaries are prebuilt native CPU profiler bindings for multiple platforms/ABI versions — core purpose of this package from Sentry. | ai |
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
3 findingsScript: node scripts/check-build.js
Package contains compiled binaries that could be backdoors: • lib/sentry_cpu_profiler-darwin-arm64-108.node • lib/sentry_cpu_profiler-darwin-arm64-115.node • lib/sentry_cpu_profiler-darwin-arm64-127.node • lib/sentry_cpu_profiler-darwin-arm64-137.node • lib/sentry_cpu_profiler-darwin-x64-108.node • lib/sentry_cpu_profiler-darwin-x64-115.node • lib/sentry_cpu_profiler-darwin-x64-127.node • lib/sentry_cpu_profiler-darwin-x64-137.node • lib/sentry_cpu_profiler-linux-arm64-glibc-108.node • lib/sentry_cpu_profiler-linux-arm64-glibc-115.node ... and 18 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.