⌁runtimereadySTATIC COMPATIBILITY INTELLIGENCE
SAVED COMPATIBILITY REPORT

plaid@48.0.0
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 plaid@48.0.0 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 >=10.0.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
Unknown
APIs
Unknown
SSR
Unknown

13 packages and 90 files scanned. At least one file scan was incomplete. Coverage describes the inspected scope, not every possible code path.

FILE AND DEPENDENCY EVIDENCE

12 findings to review

1. 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. Check the package's documented exports for a supported ESM or browser entry. Import public exported paths rather than guessing internal file paths.
  2. 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.
  3. 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/index.js
Dependency path
plaid@48.0.0
Entry points
dist/index.js
Dimension
import
Reachability
selected entry
Confidence
medium · static

2. Filesystem API

Unknown

Imports fs

Source excerpt

lib/form_data.js:9:10 · first detected occurrence

var https = require('https');
var parseUrl = require('url').parse;
var fs = require('fs');
var Stream = require('stream').Stream;
var crypto = require('crypto');

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/form_data.js
Dependency path
plaid@48.0.0 → axios@1.20.0 → form-data@4.0.6
Entry points
lib/form_data
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.

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/form_data
Dependency path
plaid@48.0.0 → axios@1.20.0 → form-data@4.0.6
Entry points
lib/form_data
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · 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.

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
plaid@48.0.0 → axios@1.20.0 → follow-redirects@1.16.1
Entry points
index.js
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static

5. Node built-in

Unknown

Imports net

Source excerpt

dist/agent.js:15:31 · first detected occurrence

};
Object.defineProperty(exports, "__esModule", { value: true });
const net_1 = __importDefault(require("net"));
const tls_1 = __importDefault(require("tls"));
const url_1 = __importDefault(require("url"));

Suggested next steps

Verify the exact Node API being used
  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. Inspect which methods are called, then compare those methods with the target runtime's API support. An import that resolves may still expose unsupported methods.
  3. If required methods are unavailable, choose an exported runtime-specific entry, replace the operation with supported APIs, or run that part of the application in a supported Node environment.
  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
dist/agent.js
Dependency path
plaid@48.0.0 → axios@1.20.0 → https-proxy-agent@5.0.1
Entry points
dist/index
Dimension
apis
Reachability
not proven reachable from selected entry
Confidence
low · static

6. Node built-in

Unknown

Imports tls

Source excerpt

dist/agent.js:16:31 · first detected occurrence

Object.defineProperty(exports, "__esModule", { value: true });
const net_1 = __importDefault(require("net"));
const tls_1 = __importDefault(require("tls"));
const url_1 = __importDefault(require("url"));
const assert_1 = __importDefault(require("assert"));

Suggested next steps

Verify the exact Node API being used
  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. Inspect which methods are called, then compare those methods with the target runtime's API support. An import that resolves may still expose unsupported methods.
  3. If required methods are unavailable, choose an exported runtime-specific entry, replace the operation with supported APIs, or run that part of the application in a supported Node environment.
  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
dist/agent.js
Dependency path
plaid@48.0.0 → axios@1.20.0 → https-proxy-agent@5.0.1
Entry points
dist/index
Dimension
apis
Reachability
not proven reachable from selected entry
Confidence
low · static

7. 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
dist/index
Dependency path
plaid@48.0.0 → axios@1.20.0 → https-proxy-agent@5.0.1
Entry points
dist/index
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static

8. 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
plaid@48.0.0 → axios@1.20.0 → form-data@4.0.6 → asynckit@0.4.0
Entry points
index.js
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
plaid@48.0.0 → axios@1.20.0 → form-data@4.0.6 → mime-types@2.1.35
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
lib/combined_stream
Dependency path
plaid@48.0.0 → axios@1.20.0 → form-data@4.0.6 → combined-stream@1.0.8
Entry points
lib/combined_stream
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static

11. 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
src/index.js
Dependency path
plaid@48.0.0 → axios@1.20.0 → https-proxy-agent@5.0.1 → debug@4.4.3
Entry points
src/index.js
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static

12. 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
dist/src/index
Dependency path
plaid@48.0.0 → axios@1.20.0 → https-proxy-agent@5.0.1 → agent-base@6.0.2
Entry points
dist/src/index
Dimension
import
Reachability
not proven reachable from selected entry
Confidence
low · static

How to use this report

This report preserves the findings as of October 15, 2026 at 12:15 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 ↗