What compatibility issues were found on Cloudflare Workers?
The saved analysis assesses axios@1.7.9 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.
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
Likely compatible
APIs
Unknown
SSR
Likely compatible
15 packages and 113 files scanned. Coverage describes the inspected scope, not every possible code path.
Check the storage operation and execution environment
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Identify which filesystem operation is used and whether your target runtime implements that operation with the required persistence and permissions.
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.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
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.
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
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
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.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
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.
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
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
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.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
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.
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
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
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.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
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.
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
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
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.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
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.
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
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
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.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
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.
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
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
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.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
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.
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
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
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.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
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.
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
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
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.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
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.
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
First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
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.
This finding is in a transitive dependency. Prefer upgrading/configuring its parent package or proposing an upstream fix over editing installed node_modules.
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.
This report preserves the findings as of October 4, 2026 at 8:08 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.