⌁runtimereadySTATIC COMPATIBILITY INTELLIGENCE
SAVED COMPATIBILITY REPORT

sharp@0.35.5
on Cloudflare Workers

Analyzed · Static analysis only

A saved snapshot, not a live compatibility guarantee. Opening this page does not run a scan.

Analyze a package ↗Methodology and limitations

What compatibility issues were found on Cloudflare Workers?

The saved analysis assesses sharp@0.35.5 as potential issue for Cloudflare Workers. Review the findings and coverage below; this is not a runtime execution test.

Potential issue

Not scored · low confidence

No detected blocker within scan limits does not mean verified execution. Scores are heuristics, not probabilities.

Score withheld: inspection is incomplete or runtime support is unresolved.

Assessment assumptions
  • Broad runtime profile; no exact runtime version, platform, or deployment configuration was selected.
  • Package declares Node.js >=20.9.0. This constraint has not been checked against a selected version and does not declare Bun or Deno support.
  • Node API support depends on Workers compatibility settings and the specific operation. Native Node addons and runtime eval are unavailable in this profile.
import
Potential issue
execute
Potential issue
APIs
Potential issue
SSR
Unknown

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.

FILE AND DEPENDENCY EVIDENCE

26 findings to review

1. Child process API

Potential issue

Imports node:child_process

Source excerpt

dist/libvips.cjs:6:23 · first detected occurrence

*/

const { spawnSync } = require('node:child_process');
const { createHash } = require('node:crypto');
const semver = require('semver');

Suggested next steps

Isolate subprocess-dependent work
  1. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  2. Check whether the dependency actually launches a process on your code path.
  3. If subprocess execution is required and unavailable, move that work to a backend or job service that supports it, or use a library that performs the operation without launching a process.
  4. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
dist/libvips.cjs
Dependency path
sharp@0.35.5
Entry points
dist/index.mjs
Dimension
apis
Reachability
not proven reachable from selected entry
Confidence
low · static

2. Dynamic require

Potential issue

Computed require() cannot be resolved statically

Source excerpt

dist/libvips.cjs:54:12 · first detected occurrence

const buildSharpLibvipsIncludeDir = () => {
  try {
    return require(`@img/sharp-libvips-dev-${buildPlatformArch()}/include`);
  } catch {
    try {

Suggested next steps

Make the possible imports explicit
  1. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  2. Identify the possible values passed to require() and check whether the target loader or bundler can include them.
  3. If you control the source, replace computed paths with a bounded map of literal imports where practical. Otherwise, use the package's documented bundler integration or request an upstream fix.
  4. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
dist/libvips.cjs
Dependency path
sharp@0.35.5
Entry points
dist/index.mjs
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static

3. Child process API

Potential issue

Imports node:child_process

Source excerpt

dist/libvips.mjs:6:1 · first detected occurrence

*/

import { spawnSync } from 'node:child_process';
import { createHash } from 'node:crypto';
import semver from 'semver';

Suggested next steps

Isolate subprocess-dependent work
  1. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  2. Check whether the dependency actually launches a process on your code path.
  3. If subprocess execution is required and unavailable, move that work to a backend or job service that supports it, or use a library that performs the operation without launching a process.
  4. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
dist/libvips.mjs
Dependency path
sharp@0.35.5
Entry points
dist/index.mjs
Dimension
apis
Reachability
not proven reachable from selected entry
Confidence
low · static

4. Dynamic require

Potential issue

Computed require() cannot be resolved statically

Source excerpt

dist/libvips.mjs:54:12 · first detected occurrence

const buildSharpLibvipsIncludeDir = () => {
  try {
    return require(`@img/sharp-libvips-dev-${buildPlatformArch()}/include`);
  } catch {
    try {

Suggested next steps

Make the possible imports explicit
  1. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  2. Identify the possible values passed to require() and check whether the target loader or bundler can include them.
  3. If you control the source, replace computed paths with a bounded map of literal imports where practical. Otherwise, use the package's documented bundler integration or request an upstream fix.
  4. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
dist/libvips.mjs
Dependency path
sharp@0.35.5
Entry points
dist/index.mjs
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static

5. Dynamic require

Potential issue

Computed require() cannot be resolved statically

Source excerpt

dist/sharp.cjs:25:11 · first detected occurrence

const errors = [];
try {
  sharp = require(`../src/build/Release/sharp-${runtimePlatform}-${version}.node`);
} catch (err) {
  errors.push(err);

Suggested next steps

Make the possible imports explicit
  1. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  2. Identify the possible values passed to require() and check whether the target loader or bundler can include them.
  3. If you control the source, replace computed paths with a bounded map of literal imports where practical. Otherwise, use the package's documented bundler integration or request an upstream fix.
  4. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
dist/sharp.cjs
Dependency path
sharp@0.35.5
Entry points
dist/index.mjs
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static

6. Dynamic require

Potential issue

Computed require() cannot be resolved statically

Source excerpt

dist/sharp.mjs:25:11 · first detected occurrence

const errors = [];
try {
  sharp = require(`../src/build/Release/sharp-${runtimePlatform}-${version}.node`);
} catch (err) {
  errors.push(err);

Suggested next steps

Make the possible imports explicit
  1. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  2. Identify the possible values passed to require() and check whether the target loader or bundler can include them.
  3. If you control the source, replace computed paths with a bounded map of literal imports where practical. Otherwise, use the package's documented bundler integration or request an upstream fix.
  4. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
dist/sharp.mjs
Dependency path
sharp@0.35.5
Entry points
dist/index.mjs
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static

7. Dynamic require

Potential issue

Computed require() cannot be resolved statically

Source excerpt

dist/utility.cjs:68:18 · first detected occurrence

  if (!libvipsVersion.isWasm) {
    try {
      versions = require(`@img/sharp-${runtimePlatform}/versions`);
    } catch (_) {
      try {

Suggested next steps

Make the possible imports explicit
  1. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  2. Identify the possible values passed to require() and check whether the target loader or bundler can include them.
  3. If you control the source, replace computed paths with a bounded map of literal imports where practical. Otherwise, use the package's documented bundler integration or request an upstream fix.
  4. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
dist/utility.cjs
Dependency path
sharp@0.35.5
Entry points
dist/index.mjs
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static

8. Dynamic require

Potential issue

Computed require() cannot be resolved statically

Source excerpt

dist/utility.mjs:68:18 · first detected occurrence

  if (!libvipsVersion.isWasm) {
    try {
      versions = require(`@img/sharp-${runtimePlatform}/versions`);
    } catch (_) {
      try {

Suggested next steps

Make the possible imports explicit
  1. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  2. Identify the possible values passed to require() and check whether the target loader or bundler can include them.
  3. If you control the source, replace computed paths with a bounded map of literal imports where practical. Otherwise, use the package's documented bundler integration or request an upstream fix.
  4. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
dist/utility.mjs
Dependency path
sharp@0.35.5
Entry points
dist/index.mjs
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static

9. CommonJS entry

Potential issue

Selected entry appears to use CommonJS; this runtime may need bundler interop

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Review the package's module entry points
  1. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  2. Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
  3. If only CommonJS is available, test your build tool's CommonJS conversion and interop behavior. Changing your own package to type: module does not convert a dependency's CommonJS source.
  4. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  5. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
index.js
Dependency path
sharp@0.35.5 → semver@7.8.5
Entry points
index.js
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static

10. CommonJS entry

Potential issue

Selected entry appears to use CommonJS; this runtime may need bundler interop

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Review the package's module entry points
  1. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  2. Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
  3. If only CommonJS is available, test your build tool's CommonJS conversion and interop behavior. Changing your own package to type: module does not convert a dependency's CommonJS source.
  4. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  5. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
index.cjs
Dependency path
sharp@0.35.5 → @img/colour@1.1.0
Entry points
index.cjs
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static

11. Child process API

Potential issue

Imports child_process

Source excerpt

lib/detect-libc.js:6:22 · first detected occurrence

'use strict';

const childProcess = require('child_process');
const { isLinux, getReport } = require('./process');
const { LDD_PATH, SELF_PATH, readFile, readFileSync } = require('./filesystem');

Suggested next steps

Isolate subprocess-dependent work
  1. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  2. Check whether the dependency actually launches a process on your code path.
  3. If subprocess execution is required and unavailable, move that work to a backend or job service that supports it, or use a library that performs the operation without launching a process.
  4. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  5. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/detect-libc.js
Dependency path
sharp@0.35.5 → detect-libc@2.1.2
Entry points
lib/detect-libc.js
Dimension
apis
Reachability
not proven reachable from selected entry
Confidence
low · static

12. Filesystem API

Unknown

Imports fs

Source excerpt

lib/filesystem.js:6:12 · first detected occurrence

'use strict';

const fs = require('fs');

const LDD_PATH = '/usr/bin/ldd';

Suggested next steps

Check the storage operation and execution environment
  1. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  2. Identify which filesystem operation is used and whether your target runtime implements that operation with the required persistence and permissions.
  3. If it is needed but unsupported, move filesystem work to a supported server environment or adapt it to the runtime's storage APIs. A shim cannot supply a real filesystem.
  4. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  5. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/filesystem.js
Dependency path
sharp@0.35.5 → detect-libc@2.1.2
Entry points
lib/detect-libc.js
Dimension
apis
Reachability
not proven reachable from selected entry
Confidence
low · static

13. CommonJS entry

Potential issue

Selected entry appears to use CommonJS; this runtime may need bundler interop

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Review the package's module entry points
  1. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  2. Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
  3. If only CommonJS is available, test your build tool's CommonJS conversion and interop behavior. Changing your own package to type: module does not convert a dependency's CommonJS source.
  4. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  5. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/detect-libc.js
Dependency path
sharp@0.35.5 → detect-libc@2.1.2
Entry points
lib/detect-libc.js
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static

14. Native addon

Potential issue

Native addon artifact; Node-API symbol detected

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Check for a portable implementation
  1. First confirm whether this optional dependency is selected for your deployment platform and feature set.
  2. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  3. Check whether the native artifact is required on your platform or whether the package provides a documented JavaScript or WebAssembly fallback.
  4. If the native addon is required, use a runtime and deployment platform that support its binary/ABI and installation requirements. Do not assume that bundling or Node compatibility flags make native binaries portable.
  5. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  6. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/sharp-linux-arm-0.35.5.node
Dependency path
sharp@0.35.5 → @img/sharp-linux-arm@0.35.5
Entry points
index.js
Dimension
execute
Reachability
optional dependency; platform selection not verified
Confidence
low · static

15. Native addon

Potential issue

Native addon artifact; Node-API symbol detected

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Check for a portable implementation
  1. First confirm whether this optional dependency is selected for your deployment platform and feature set.
  2. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  3. Check whether the native artifact is required on your platform or whether the package provides a documented JavaScript or WebAssembly fallback.
  4. If the native addon is required, use a runtime and deployment platform that support its binary/ABI and installation requirements. Do not assume that bundling or Node compatibility flags make native binaries portable.
  5. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  6. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/sharp-linux-x64-0.35.5.node
Dependency path
sharp@0.35.5 → @img/sharp-linux-x64@0.35.5
Entry points
index.js
Dimension
execute
Reachability
optional dependency; platform selection not verified
Confidence
low · static

16. Native addon

Potential issue

Native addon artifact; Node-API symbol detected

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Check for a portable implementation
  1. First confirm whether this optional dependency is selected for your deployment platform and feature set.
  2. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  3. Check whether the native artifact is required on your platform or whether the package provides a documented JavaScript or WebAssembly fallback.
  4. If the native addon is required, use a runtime and deployment platform that support its binary/ABI and installation requirements. Do not assume that bundling or Node compatibility flags make native binaries portable.
  5. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  6. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/sharp-win32-x64-0.35.5.node
Dependency path
sharp@0.35.5 → @img/sharp-win32-x64@0.35.5
Entry points
index.js
Dimension
execute
Reachability
optional dependency; platform selection not verified
Confidence
low · static

17. Native addon

Potential issue

Native addon artifact; Node-API symbol detected

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Check for a portable implementation
  1. First confirm whether this optional dependency is selected for your deployment platform and feature set.
  2. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  3. Check whether the native artifact is required on your platform or whether the package provides a documented JavaScript or WebAssembly fallback.
  4. If the native addon is required, use a runtime and deployment platform that support its binary/ABI and installation requirements. Do not assume that bundling or Node compatibility flags make native binaries portable.
  5. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  6. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/sharp-darwin-x64-0.35.5.node
Dependency path
sharp@0.35.5 → @img/sharp-darwin-x64@0.35.5
Entry points
index.js
Dimension
execute
Reachability
optional dependency; platform selection not verified
Confidence
low · static

18. Native addon

Potential issue

Native addon artifact; Node-API symbol detected

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Check for a portable implementation
  1. First confirm whether this optional dependency is selected for your deployment platform and feature set.
  2. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  3. Check whether the native artifact is required on your platform or whether the package provides a documented JavaScript or WebAssembly fallback.
  4. If the native addon is required, use a runtime and deployment platform that support its binary/ABI and installation requirements. Do not assume that bundling or Node compatibility flags make native binaries portable.
  5. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  6. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/sharp-win32-ia32-0.35.5.node
Dependency path
sharp@0.35.5 → @img/sharp-win32-ia32@0.35.5
Entry points
index.js
Dimension
execute
Reachability
optional dependency; platform selection not verified
Confidence
low · static

19. Native addon

Potential issue

Native addon artifact; Node-API symbol detected

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Check for a portable implementation
  1. First confirm whether this optional dependency is selected for your deployment platform and feature set.
  2. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  3. Check whether the native artifact is required on your platform or whether the package provides a documented JavaScript or WebAssembly fallback.
  4. If the native addon is required, use a runtime and deployment platform that support its binary/ABI and installation requirements. Do not assume that bundling or Node compatibility flags make native binaries portable.
  5. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  6. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/sharp-linux-arm64-0.35.5.node
Dependency path
sharp@0.35.5 → @img/sharp-linux-arm64@0.35.5
Entry points
index.js
Dimension
execute
Reachability
optional dependency; platform selection not verified
Confidence
low · static

20. Native addon

Potential issue

Native addon artifact; Node-API symbol detected

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Check for a portable implementation
  1. First confirm whether this optional dependency is selected for your deployment platform and feature set.
  2. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  3. Check whether the native artifact is required on your platform or whether the package provides a documented JavaScript or WebAssembly fallback.
  4. If the native addon is required, use a runtime and deployment platform that support its binary/ABI and installation requirements. Do not assume that bundling or Node compatibility flags make native binaries portable.
  5. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  6. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/sharp-linux-ppc64-0.35.5.node
Dependency path
sharp@0.35.5 → @img/sharp-linux-ppc64@0.35.5
Entry points
index.js
Dimension
execute
Reachability
optional dependency; platform selection not verified
Confidence
low · static

21. Native addon

Potential issue

Native addon artifact; Node-API symbol detected

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Check for a portable implementation
  1. First confirm whether this optional dependency is selected for your deployment platform and feature set.
  2. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  3. Check whether the native artifact is required on your platform or whether the package provides a documented JavaScript or WebAssembly fallback.
  4. If the native addon is required, use a runtime and deployment platform that support its binary/ABI and installation requirements. Do not assume that bundling or Node compatibility flags make native binaries portable.
  5. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  6. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/sharp-linux-s390x-0.35.5.node
Dependency path
sharp@0.35.5 → @img/sharp-linux-s390x@0.35.5
Entry points
index.js
Dimension
execute
Reachability
optional dependency; platform selection not verified
Confidence
low · static

22. Native addon

Potential issue

Native addon artifact; Node-API symbol detected

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Check for a portable implementation
  1. First confirm whether this optional dependency is selected for your deployment platform and feature set.
  2. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  3. Check whether the native artifact is required on your platform or whether the package provides a documented JavaScript or WebAssembly fallback.
  4. If the native addon is required, use a runtime and deployment platform that support its binary/ABI and installation requirements. Do not assume that bundling or Node compatibility flags make native binaries portable.
  5. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  6. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/sharp-win32-arm64-0.35.5.node
Dependency path
sharp@0.35.5 → @img/sharp-win32-arm64@0.35.5
Entry points
index.js
Dimension
execute
Reachability
optional dependency; platform selection not verified
Confidence
low · static

23. Native addon

Potential issue

Native addon artifact; Node-API symbol detected

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Check for a portable implementation
  1. First confirm whether this optional dependency is selected for your deployment platform and feature set.
  2. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  3. Check whether the native artifact is required on your platform or whether the package provides a documented JavaScript or WebAssembly fallback.
  4. If the native addon is required, use a runtime and deployment platform that support its binary/ABI and installation requirements. Do not assume that bundling or Node compatibility flags make native binaries portable.
  5. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  6. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/sharp-darwin-arm64-0.35.5.node
Dependency path
sharp@0.35.5 → @img/sharp-darwin-arm64@0.35.5
Entry points
index.js
Dimension
execute
Reachability
optional dependency; platform selection not verified
Confidence
low · static

24. Native addon

Potential issue

Native addon artifact; Node-API symbol detected

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Check for a portable implementation
  1. First confirm whether this optional dependency is selected for your deployment platform and feature set.
  2. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  3. Check whether the native artifact is required on your platform or whether the package provides a documented JavaScript or WebAssembly fallback.
  4. If the native addon is required, use a runtime and deployment platform that support its binary/ABI and installation requirements. Do not assume that bundling or Node compatibility flags make native binaries portable.
  5. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  6. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/sharp-linux-riscv64-0.35.5.node
Dependency path
sharp@0.35.5 → @img/sharp-linux-riscv64@0.35.5
Entry points
index.js
Dimension
execute
Reachability
optional dependency; platform selection not verified
Confidence
low · static

25. Native addon

Potential issue

Native addon artifact; Node-API symbol detected

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Check for a portable implementation
  1. First confirm whether this optional dependency is selected for your deployment platform and feature set.
  2. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  3. Check whether the native artifact is required on your platform or whether the package provides a documented JavaScript or WebAssembly fallback.
  4. If the native addon is required, use a runtime and deployment platform that support its binary/ABI and installation requirements. Do not assume that bundling or Node compatibility flags make native binaries portable.
  5. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  6. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/sharp-linuxmusl-x64-0.35.5.node
Dependency path
sharp@0.35.5 → @img/sharp-linuxmusl-x64@0.35.5
Entry points
index.js
Dimension
execute
Reachability
optional dependency; platform selection not verified
Confidence
low · static

26. Native addon

Potential issue

Native addon artifact; Node-API symbol detected

Source excerpt

No source excerpt was saved for this finding. Older reports, manifest or binary signals, and inspection failures may not have a source location.

Suggested next steps

Check for a portable implementation
  1. First confirm whether this optional dependency is selected for your deployment platform and feature set.
  2. First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
  3. Check whether the native artifact is required on your platform or whether the package provides a documented JavaScript or WebAssembly fallback.
  4. If the native addon is required, use a runtime and deployment platform that support its binary/ABI and installation requirements. Do not assume that bundling or Node compatibility flags make native binaries portable.
  5. This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
  6. Check your Workers compatibility date and Node API support before making changes. This analyzer uses a coarse profile and does not model every compatibility flag or API implementation.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

File
lib/sharp-linuxmusl-arm64-0.35.5.node
Dependency path
sharp@0.35.5 → @img/sharp-linuxmusl-arm64@0.35.5
Entry points
index.js
Dimension
execute
Reachability
optional dependency; platform selection not verified
Confidence
low · static

How to use this report

This report preserves the findings as of October 12, 2026 at 9:41 AM UTC. It may use older analysis rules (analysis version 4). 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 ↗