1. Native addon
Potential issueNative addon artifact or build manifest
- File
src/binding.gyp- Dependency path
sharp@0.35.5- Entry points
dist/index.mjs- Dimension
- execute
- Reachability
- not proven reachable from selected entry
- Confidence
- low · static
Analyzed · Static analysis only
A saved snapshot, not a live compatibility guarantee. Opening this page does not run a scan.
The saved analysis assesses sharp@0.35.5 as potential issue for Browser. Review the findings and coverage below; this is not a runtime execution test.
65/100 heuristic score · low confidence
26 packages and 124 files scanned. Dependency graph inspection was capped. At least one file scan was incomplete. Coverage describes the inspected scope, not every possible code path.
Native addon artifact or build manifest
src/binding.gypsharp@0.35.5dist/index.mjsImports node:child_process
dist/libvips.cjssharp@0.35.5dist/index.mjsComputed require() cannot be resolved statically
dist/libvips.cjssharp@0.35.5dist/index.mjsImports node:child_process
dist/libvips.mjssharp@0.35.5dist/index.mjsComputed require() cannot be resolved statically
dist/libvips.mjssharp@0.35.5dist/index.mjsComputed require() cannot be resolved statically
dist/sharp.cjssharp@0.35.5dist/index.mjsComputed require() cannot be resolved statically
dist/sharp.mjssharp@0.35.5dist/index.mjsComputed require() cannot be resolved statically
dist/utility.cjssharp@0.35.5dist/index.mjsComputed require() cannot be resolved statically
dist/utility.mjssharp@0.35.5dist/index.mjsSelected entry appears to use CommonJS; this runtime may need bundler interop
index.jssharp@0.35.5 → semver@7.8.5index.jsSelected entry appears to use CommonJS; this runtime may need bundler interop
index.cjssharp@0.35.5 → @img/colour@1.1.0index.cjsImports child_process
lib/detect-libc.jssharp@0.35.5 → detect-libc@2.1.2lib/detect-libc.jsImports fs
lib/filesystem.jssharp@0.35.5 → detect-libc@2.1.2lib/detect-libc.jsSelected entry appears to use CommonJS; this runtime may need bundler interop
lib/detect-libc.jssharp@0.35.5 → detect-libc@2.1.2lib/detect-libc.jsNative addon artifact or build manifest
lib/sharp-linux-arm-0.35.5.nodesharp@0.35.5 → @img/sharp-linux-arm@0.35.5index.jsNative addon artifact or build manifest
lib/sharp-linux-x64-0.35.5.nodesharp@0.35.5 → @img/sharp-linux-x64@0.35.5index.jsNative addon artifact or build manifest
lib/sharp-win32-x64-0.35.5.nodesharp@0.35.5 → @img/sharp-win32-x64@0.35.5index.jsNative addon artifact or build manifest
lib/sharp-darwin-x64-0.35.5.nodesharp@0.35.5 → @img/sharp-darwin-x64@0.35.5index.jsNative addon artifact or build manifest
lib/sharp-win32-ia32-0.35.5.nodesharp@0.35.5 → @img/sharp-win32-ia32@0.35.5index.jsNative addon artifact or build manifest
lib/sharp-linux-arm64-0.35.5.nodesharp@0.35.5 → @img/sharp-linux-arm64@0.35.5index.jsNative addon artifact or build manifest
lib/sharp-linux-ppc64-0.35.5.nodesharp@0.35.5 → @img/sharp-linux-ppc64@0.35.5index.jsNative addon artifact or build manifest
lib/sharp-linux-s390x-0.35.5.nodesharp@0.35.5 → @img/sharp-linux-s390x@0.35.5index.jsNative addon artifact or build manifest
lib/sharp-win32-arm64-0.35.5.nodesharp@0.35.5 → @img/sharp-win32-arm64@0.35.5index.jsNative addon artifact or build manifest
lib/sharp-darwin-arm64-0.35.5.nodesharp@0.35.5 → @img/sharp-darwin-arm64@0.35.5index.jsNative addon artifact or build manifest
lib/sharp-linux-riscv64-0.35.5.nodesharp@0.35.5 → @img/sharp-linux-riscv64@0.35.5index.jsNative addon artifact or build manifest
lib/sharp-linuxmusl-x64-0.35.5.nodesharp@0.35.5 → @img/sharp-linuxmusl-x64@0.35.5index.jsNative addon artifact or build manifest
lib/sharp-linuxmusl-arm64-0.35.5.nodesharp@0.35.5 → @img/sharp-linuxmusl-arm64@0.35.5index.jsThis report preserves the findings as of September 28, 2026 at 7:15 PM UTC. It may use older analysis rules (analysis version 2). Package code was not executed. Runtime versions, flags, bundlers, and operating systems can change actual compatibility.
Reachability is approximate. Optional dependencies, generated code, dynamic imports, and incomplete scans can cause false positives or missed issues. A green assessment means no blocker was found within the inspected scope. The score is a heuristic, not a probability.
Read all limitations ↗