What compatibility issues were found on Vercel Edge?
The saved analysis assesses local@0.3.3 as likely incompatible for Vercel Edge. Review the findings and coverage below; this is not a runtime execution test.
Likely incompatible
41/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
Likely incompatible
SSR
Unknown
3 packages and 93 files scanned. At least one file scan was incomplete. Coverage describes the inspected scope, not every possible code path.
FILE AND DEPENDENCY EVIDENCE
5 findings to review
1. Filesystem API
Likely incompatible
Imports fs
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
index.js
Dependency path
local@0.3.3
Entry points
index.js
Dimension
apis
Reachability
selected entry
Confidence
medium · static
2. Filesystem API
Potential issue
Imports fs
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
drivers/fileSystem.js
Dependency path
local@0.3.3
Entry points
index.js
Dimension
apis
Reachability
not proven reachable from selected entry
Confidence
low · static
3. 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.
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
index.js
Dependency path
local@0.3.3
Entry points
index.js
Dimension
import
Reachability
selected entry
Confidence
medium · static
4. 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.
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/async.js
Dependency path
local@0.3.3 → async@2.6.4
Entry points
dist/async.js
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static
5. 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.
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
lodash.js
Dependency path
local@0.3.3 → async@2.6.4 → lodash@4.18.1
Entry points
lodash.js
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 29, 2026 at 4:36 AM 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.