@instana/autoprofile
Automatic Node.js 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): aryamohanan is a named contributor (IBM email) with 51 approved packages; transition is within the Instana/IBM org. | ai | |
| install-scripts | install-script:install | AI (install-scripts): node-gyp-build is the standard prebuilt-binary loader for native addons; stable for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node binaries for multiple platforms are expected for this native profiler addon. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads package.json via path.join — benign pattern, not arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:nan | AI (phantom-deps): nan is a native addon build dependency referenced in binding.gyp, not directly imported in JS. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 5 / 0 | |
| 5.5.0 | 5 / 0 | |
| 5.4.3 | 5 / 0 | |
| 5.4.2 | 5 / 0 | |
| 5.4.0 | 5 / 0 | |
| 5.2.2 | 5 / 0 | |
| 5.0.2 | 5 / 0 | |
| 4.29.0 | 5 / 0 | |
| 4.27.1 | 5 / 0 |
v6.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • prebuilds/linux-arm/node.abi108.armv6.node • prebuilds/linux-arm/node.abi108.armv7.node • prebuilds/linux-arm64/node.abi108.armv8.node • prebuilds/linux-x64/node.abi108.glibc.node • prebuilds/linux-x64/node.abi108.musl.node • prebuilds/linux-s390x/node.abi108.node • prebuilds/linux-arm/node.abi115.armv6.node • prebuilds/linux-arm/node.abi115.armv7.node • prebuilds/linux-arm64/node.abi115.armv8.node • prebuilds/linux-x64/node.abi115.glibc.node ... and 13 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.