@contrast/fn-inspect
Retrieve function name and line number from a function reference
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 |
|---|---|---|---|---|
| install-scripts | install-script:install | AI (install-scripts): Standard node-gyp-build prebuilt binary loader; stable pattern for this native addon package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node files for multiple platforms/ABIs are expected for this native addon; matches prebuildify build workflow. | 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 | |
| phantom-deps | phantom-dep:node-abi | AI (phantom-deps): node-abi is used by build scripts for ABI resolution, not directly imported in JS. | ai |
v5.0.2
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • prebuilds/linux-arm64/@contrast+fn-inspect.abi108.armv8.node • prebuilds/linux-x64/@contrast+fn-inspect.abi108.glibc.node • prebuilds/linux-x64/@contrast+fn-inspect.abi108.musl.node • prebuilds/win32-x64/@contrast+fn-inspect.abi108.node • prebuilds/linux-arm64/@contrast+fn-inspect.abi115.armv8.node • prebuilds/linux-x64/@contrast+fn-inspect.abi115.glibc.node • prebuilds/linux-x64/@contrast+fn-inspect.abi115.musl.node • prebuilds/win32-x64/@contrast+fn-inspect.abi115.node • prebuilds/linux-arm64/@contrast+fn-inspect.abi127.armv8.node • prebuilds/linux-x64/@contrast+fn-inspect.abi127.glibc.node ... and 6 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.