[Snyk] Upgrade: async, debug, morgan, serve-favicon, web3 #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![snyk-io[bot]](https://avatars.githubusercontent.com/in/372950?s=60&v=4){kind=small}
Snyk has created this PR to upgrade:
- async from 2.6.4 to 3.2.6.
See this package in npm: https://www.npmjs.com/package/async
- debug from 2.6.9 to 4.3.6.
See this package in npm: https://www.npmjs.com/package/debug
- morgan from 1.7.0 to 1.10.0.
See this package in npm: https://www.npmjs.com/package/morgan
- serve-favicon from 2.3.2 to 2.5.0.
See this package in npm: https://www.npmjs.com/package/serve-favicon
- web3 from 0.19.1 to 4.12.1.
See this package in npm: https://www.npmjs.com/package/web3
See this project in Snyk:
https://app.snyk.io/org/sherfeyinv/project/8facbec7-4ac7-4dc0-ba96-1b7f2762d9fd?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade multiple dependencies.
👯♂ The following dependencies are linked and will therefore be updated together.ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
async
⚠️ This is a major version upgrade, and may be a breaking change | a month ago
⚠️ This is a major version upgrade, and may be a breaking change | 2 months ago
⚠️ This is a major version upgrade, and may be a breaking change | a month ago
from 2.6.4 to 3.2.6 | 12 versions ahead of your current version
on 2024-08-19
debug
from 2.6.9 to 4.3.6 | 23 versions ahead of your current version
on 2024-07-27
morgan
from 1.7.0 to 1.10.0 | 6 versions ahead of your current version | 5 years ago
on 2020-03-20
serve-favicon
from 2.3.2 to 2.5.0 | 7 versions ahead of your current version | 6 years ago
on 2018-03-29
web3
from 0.19.1 to 4.12.1 | 451 versions ahead of your current version
on 2024-08-23
Issues fixed by the recommended upgrade:
SNYK-JS-CRYPTOJS-6028119
SNYK-JS-MORGAN-72579
Release notes
Package name: async
-
3.2.6 - 2024-08-19
-
3.2.5 - 2023-11-03
-
3.2.4 - 2022-06-07
-
3.2.3 - 2022-01-10
-
3.2.2 - 2021-10-28
-
3.2.1 - 2021-08-05
-
3.2.0 - 2020-02-24
-
3.1.1 - 2020-01-24
-
3.1.0 - 2019-06-23
-
3.0.1 - 2019-05-26
-
3.0.1-0 - 2018-10-01
-
3.0.0 - 2019-05-20
-
2.6.4 - 2022-04-13
from async GitHub release notesVersion 3.2.6
Version 3.2.5
Version 3.2.4
Version 3.2.3
Version 3.2.2
Version 3.2.1
Version 3.2.0
Version 3.1.1
Version 2.6.4
Package name: debug
-
4.3.6 - 2024-07-27
- Avoid using deprecated RegExp.$1 by @ bluwy in #969
- @ bluwy made their first contribution in #969
-
4.3.5 - 2024-05-31
- cac39b1 Fix/debug depth (#926)
-
4.3.4 - 2022-03-17
- Add section about configuring JS console to show debug messages by @ gitname in #866
- Replace deprecated String.prototype.substr() by @ CommanderRoot in #876
- @ gitname made their first contribution in #866
- @ CommanderRoot made their first contribution in #876
-
4.3.3 - 2021-11-27
- Migrates repository from https://github.com/visionmedia/debug to https://github.com/debug-js/debug. Please see notes below as to why this change was made.
- Updates repository maintainership information
- Updates the copyright (no license terms change has been made)
- Removes accidental epizeuxis (#828)
- Adds README section regarding usage in child procs (#850)
- The old organization was defunct and abandoned.
- I was not an owner of the old organization and thus could not ban the non-trivial amount of spam users or the few truly abusive users from the org. This hindered my ability to properly maintain this package.
- The
- The old org has way, way too many approved members with push access, for which there was nothing I could do. This presented a pretty sizable security risk given that many packages in recent years have fallen victim to backdoors and the like due to lax security access.
-
4.3.2 - 2020-12-09
- Caches enabled statuses on a per-logger basis to speed up
-
4.3.1 - 2020-11-19
- Fixes a ReDOS regression (#458) - see #797 for details.
-
4.3.0 - 2020-09-19
- Deprecated
- Fixed quoted percent sign
- Fixed memory leak within debug instances that are created dynamically
-
4.2.0 - 2020-05-19
- Replaced phantomJS with chrome backend for browser tests
- Deprecated and later removed Changelog.md in lieu of releases page
- Removed bower.json (#602)
- Removed .eslintrc (since we've switched to XO)
- Removed .coveralls.yml
- Removed the build system that was in place for various alternate package managers
- Removed the examples folder (#650)
- Switched to
- Copied custom logger to namespace extension (#646)
- Added issue and pull request templates
- Added
- Added ability to control
- Updated dependencies
- Marked
-
4.1.1 - 2018-12-22
-
4.1.0 - 2018-10-08
-
4.0.1 - 2018-09-11
-
4.0.0 - 2018-09-11
-
3.2.7 - 2020-11-19
-
3.2.6 - 2018-10-10
-
3.2.5 - 2018-09-11
-
3.2.4 - 2018-09-11
-
3.2.3 - 2018-09-11
-
3.2.2 - 2018-09-11
-
3.2.1 - 2018-09-11
-
3.2.0 - 2018-09-11
-
3.1.0 - 2017-09-26
-
3.0.1 - 2017-08-24
-
3.0.0 - 2017-08-08
-
2.6.9 - 2017-09-22
from debug GitHub release notesWhat's Changed
New Contributors
Full Changelog: 4.3.5...4.3.6
Patch
Thank you @ calvintwr for the fix.
What's Changed
New Contributors
Full Changelog: 4.3.3...4.3.4
Patch Release 4.3.3
This is a documentation-only release. Further, the repository was transferred. Please see notes below.
Thank you to @ taylor1791 and @ kristofkalocsai for their contributions.
Repository Migration Information
I've formatted this as a FAQ, please feel free to open an issue for any additional question and I'll add the response here.
Q: What impact will this have on me?
In most cases, you shouldn't notice any change.
The only exception I can think of is if you pull code directly from https://github.com/visionmedia/debug, e.g. via a
"debug": "visionmedia/debug"-type version entry in your package.json - in which case, you should still be fine due to the automatic redirection Github sets up, but you should also update any references as soon as possible.Q: What are the security implications of this change?
If you pull code directly from the old URL, you should update the URL to https://github.com/debug-js/debug as soon as possible. The old organization has many approved owners and thus a new repository could (in theory) be created at the old URL, circumventing Github's automatic redirect that is in place now and serving malicious code. I (@ Qix-) also wouldn't have access to that repository, so while I don't think it would happen, it's still something to consider.
Even in such a case, however, the officially released package on npm (
debug) would not be affected. That package is still very much under control (even more than it used to be).Q: What should I do if I encounter an issue related to the migration?
Search the issues first to see if someone has already reported it, and then open a new issue if someone has not.
Q: Why was this done as a 'patch' release? Isn't this breaking?
No, it shouldn't be breaking. The package on npm shouldn't be affected (aside from this patch release) and any references to the old repository should automatically redirect.
Thus, according to all of the "APIs" (loosely put) involved, nothing should have broken.
I understand there are a lot of edge cases so please open issues as needed so I can assist in any way necessary.
Q: Why was the repository transferred?
I'll just list them off in no particular order.
debugecosystem intends to grow beyond a single package, and since new packages could not be created in the old org (nor did it make sense for them to live there), a new org made the most sense - especially from a security point of view.Q: Was this approved?
Yes.[archive]
Q: Do I need to worry about another migration sometime in the future?
No.
Patch release 4.3.2
.enabledchecks (#799)Thank you @ omg!
Patch release 4.3.1
Minor release
debugInstance.destroy(). Future major versions will not have this method; please remove it from your codebases as it currently does nothing.Minor Release
console.debugin the browser only when it is available (#600)"engines"key to package.jsonselectColor(#747)supports-coloras an optional peer dependency3.2.7
Package name: morgan
-
1.10.0 - 2020-03-20
- Add
- Fix trailing space in colored status code for
- deps: basic-auth@~2.0.1
- deps: safe-buffer@5.1.2
- deps: depd@~2.0.0
- Replace internal
- Use instance methods on
- deps: on-headers@~1.0.2
- Fix
-
1.9.1 - 2018-09-11
- Fix using special characters in format
- deps: depd@~1.1.2
- perf: remove argument reassignment
-
1.9.0 - 2017-09-27
- Use
- deps: basic-auth@~2.0.0
- Use
- deps: debug@2.6.9
- deps: depd@~1.1.1
- Remove unnecessary
-
1.8.2 - 2017-05-24
- deps: debug@2.6.8
- Fix
- deps: ms@2.0.0
-
1.8.1 - 2017-02-11
- deps: debug@2.6.1
- Fix deprecation messages in WebStorm and other editors
- Undeprecate
-
1.8.0 - 2017-02-05
- Fix sending unnecessary
- deps: basic-auth@~1.1.0
- deps: debug@2.6.0
- Allow colors in workers
- Deprecated
- Fix error when running under React Native
- Use same color for same namespace
- deps: ms@0.7.2
- perf: enable strict mode in compiled functions
-
1.7.0 - 2016-02-19
- Add
- deps: depd@~1.1.0
- Enable strict mode in more places
- Support web browser loading
- deps: on-headers@~1.0.1
- perf: enable strict mode
from morgan GitHub release notes:total-timetokendevformatevalusage withFunctionconstructorprocessto check for listenersres.writeHeadpatch missing return valueres.headersSentwhen availablesafe-bufferfor improved Buffer APIBufferloadingDEBUG_MAX_ARRAY_LENGTHDEBUG_FDset to1or2undefinedargument to token functionsDEBUG_FDenvironment variabledigitsargument toresponse-timetokenPackage name: serve-favicon
-
2.5.0 - 2018-03-29
- Ignore requests without
- deps: ms@2.1.1
- Add
- Add
-
2.4.5 - 2017-09-26
- deps: etag@~1.8.1
- perf: replace regular expression with substring
- deps: fresh@0.5.2
- Fix regression matching multiple ETags in
- perf: improve
-
2.4.4 - 2017-09-12
- deps: fresh@0.5.1
- Fix handling of modified headers with invalid dates
- perf: improve ETag match loop
- deps: parseurl@~1.3.2
- perf: reduce overhead for full URLs
- perf: unroll the "fast-path"
- deps: safe-buffer@5.1.1
-
2.4.3 - 2017-05-16
- Use
- deps: ms@2.0.0
-
2.4.2 - 2017-03-25
- deps: ms@1.0.0
-
2.4.1 - 2017-02-28
- Remove usage of
- deps: fresh@0.5.0
- Fix incorrect result when
- Fix weak
- perf: skip checking modified time if ETag check failed
- perf: skip parsing
- perf: use
-
2.4.0 - 2017-02-20
- deps: etag@~1.8.0
- Use SHA1 instead of MD5 for ETag hashing
- Works with FIPS 140-2 OpenSSL configuration
- deps: fresh@0.4.0
- Fix false detection of
- perf: enable strict mode
- perf: hoist regular expressions
- perf: remove duplicate conditional
- perf: remove unnecessary boolean coercions
- perf: simplify initial argument checking
-
2.3.2 - 2016-11-17
- deps: ms@0.7.2
from serve-favicon GitHub release notesurlpropertyweekwIf-None-MatchIf-None-Matchtoken parsingRegExpsafe-bufferfor improved Buffer APIres._headersprivate fieldIf-None-Matchhas both*and ETagsETagmatching to match specIf-None-Matchwhen noETagheaderDate.parseinstead ofnew Dateno-cacherequest directivePackage name: web3
Hot fix
[4.12.1]
Fixed
web3-eth-accounts
TransactionFactory.registerTransactionTypeif there is a version mistatch betweenweb3-ethandweb3-eth-accountsand fix nextjs problem. (#7216)What's Changed
[4.12.0]
Fixed
web3-core
setConfig()fix forsetMaxListenerWarningThresholdfix (#5079)web3-eth-accounts
TransactionFactory.registerTransactionTypenot working, if there is a version mistatch betweenweb3-ethandweb3-eth-accountsby savingextraTxTypesatglobals. (#7197)Added
web3-eth-accounts
signMessageWithPrivateKey(#7174)web3-eth-contract
populateTransactionto thecontract.deploy(...)properties. (#7197)web3-providers-http
statusCodeof response in ResponseError,statusCodeis optional property in ResponseError.web3-rpc-providers
HttpProviderOptions | SocketOptionsinWeb3ExternalProviderandQuickNodeProviderfor provider configsweb3-errors
statusCodeproperty of response in ResponseError.Changed
web3-eth-contract
contract.deploy(...)are structured with a newly created class namedDeployerMethodClass. (#7197)abiparameter, atdataInputEncodeMethodHelperandgetSendTxParams. (#7197)What's Changed
New Contributors
[4.11.1]
Fixed
web3-errors
Eip838ExecutionErrorconstructor (#6905)web3-eth
getTransactionReceiptto not be casted asTransactionReceiptto give proper return type (#7159)web3
What's Changed
New Contributors
Full Changelog: v4.11.0...v4.11.1
[4.11.0]
Fixed
web3-eth-abi
web3-utils
_sendPendingRequestswill catch unhandled errors from_sendToSocket(#6968)web3-eth
Changed
web3-eth-accounts
web3-providers-ws
web3-rpc-providers
Promise<ResultType>toPromise<JsonRpcResponseWithResult<ResultType>>(#7102)Added
web3-eth-contract
populateTransactionwas added to contract methods (#7124)setTransactionMiddlewareandgetTransactionMiddlewarefor automatically passing tosentTransactionfordeployandsendfunctions (#7138)web3-rpc-providers
web3
web3.eth.Contractwill get transaction middleware and use it, ifweb3.ethhas transaction middleware. (#7138)[4.10.0]
Added
web3
web3-core
web3-eth
sendTransactioninrpc_method_wrappersaccepts optional param ofTransactionMiddleware(#7088)setTransactionMiddlewareandgetTransactionMiddlewarefor automatically passing tosentTransaction(#7088)web3-eth-ens
getTextnow supports first param AddressgetNamehas optional second param checkInterfaceSupportweb3-types
resultas optionalneveranderroras optionalnever in typeJsonRpcNotification` (#7091)JsonRpcNotficationas a union type inJsonRpcResponse(#7091)web3-rpc-providers
Fixed
web3-eth-ens
getNamereverse resolutionWhat's Changed