The saved analysis assesses sharp@0.35.5 as potential issue for Bun. Review the findings and coverage below; this is not a runtime execution test.
Potential issue
54/100 · low confidence
No detected blocker within scan limits does not mean verified execution. Scores are heuristics, not probabilities.
import
Potential issue
execute
Unknown
APIs
Unknown
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
6 findings to review
1. Dynamic require
Potential issue
Computed require() cannot be resolved statically
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.
This snapshot has no saved remediation guidance. Run an analysis from the analyzer to create a current report; this saved report will remain unchanged.
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
2. Dynamic require
Potential issue
Computed require() cannot be resolved statically
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.
This snapshot has no saved remediation guidance. Run an analysis from the analyzer to create a current report; this saved report will remain unchanged.
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
3. Dynamic require
Potential issue
Computed require() cannot be resolved statically
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.
This snapshot has no saved remediation guidance. Run an analysis from the analyzer to create a current report; this saved report will remain unchanged.
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
4. Dynamic require
Potential issue
Computed require() cannot be resolved statically
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.
This snapshot has no saved remediation guidance. Run an analysis from the analyzer to create a current report; this saved report will remain unchanged.
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
5. Dynamic require
Potential issue
Computed require() cannot be resolved statically
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.
This snapshot has no saved remediation guidance. Run an analysis from the analyzer to create a current report; this saved report will remain unchanged.
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
6. Dynamic require
Potential issue
Computed require() cannot be resolved statically
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.
This snapshot has no saved remediation guidance. Run an analysis from the analyzer to create a current report; this saved report will remain unchanged.
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
How to use this report
This 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.