-
Notifications
You must be signed in to change notification settings - Fork 536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request module (jsforce dependency) is deprecated #999
Comments
Does anyone know if an existing maintainer (or someone else) is looking into this ? |
This issue has been open for a long time and now is subject to security vulnerability (see https://nvd.nist.gov/vuln/detail/CVE-2023-28155). |
quick update: aside from security fixes, we aren't doing any feature work on jsforce v1. Will close this once jsforce v3 is GA. |
Hi @cristiand391, Since this is a security vulnerability, do you have any expected date for the fix to be released? |
@MaPDores we are currently working on finishing jsforce v3 and don't plan to fix this in v1, see: The reason is that v2 was already refactored to use We don't have a hard deadline for the GA, but I would say about ~1 month. |
This has been like that for a long time, Is there a workaround for this? |
This should be fixed in v3, see: #1529 |
The request package has been deprecated: request/request#3142. Additionally, its latest published version, 2.88.2, adds a deprecation warning whenever it is npm-installed. I don't think this is an issue immediately for jsforce but presumably will be should that package be updated in the lockfile.
Alternatives have been listed at: request/request#3143
The text was updated successfully, but these errors were encountered: