Skip to content
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

[Snyk] Upgrade: redux, react-redux, react-scripts, redux-thunk, styled-components, web3-eth-contract, web3 #6

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

BitcoinOutput
Copy link
Owner

snyk-top-banner

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.

Name Versions Released on

redux
from 4.1.1 to 4.2.1 | 4 versions ahead of your current version | 2 years ago
on 2023-01-28
react-redux
from 7.2.5 to 7.2.9 | 4 versions ahead of your current version | 2 years ago
on 2022-09-23
react-scripts
from 2.1.3 to 2.1.8 | 5 versions ahead of your current version | 6 years ago
on 2019-03-07
redux-thunk
from 2.3.0 to 2.4.2 | 3 versions ahead of your current version | 2 years ago
on 2022-11-04
styled-components
from 5.3.1 to 5.3.11 | 10 versions ahead of your current version | a year ago
on 2023-05-26
web3-eth-contract
from 1.8.2 to 1.10.4 | 11 versions ahead of your current version | 7 months ago
on 2024-02-05
web3
from 1.8.2 to 1.10.4 | 11 versions ahead of your current version | 7 months ago
on 2024-02-05

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
696 Proof of Concept
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
696 Proof of Concept
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
696 Proof of Concept
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-ES5EXT-6095076
696 Proof of Concept
high severity Improper Input Validation
SNYK-JS-FOLLOWREDIRECTS-6141137
696 Proof of Concept
high severity Arbitrary File Overwrite
SNYK-JS-TAR-1536528
696 No Known Exploit
high severity Prototype Pollution
SNYK-JS-INI-1048974
696 Proof of Concept
high severity Server-side Request Forgery (SSRF)
SNYK-JS-IP-6240864
696 Proof of Concept
high severity Arbitrary File Overwrite
SNYK-JS-TAR-1536531
696 No Known Exploit
high severity Arbitrary File Write
SNYK-JS-TAR-1579147
696 No Known Exploit
high severity Arbitrary File Write
SNYK-JS-TAR-1579152
696 No Known Exploit
high severity Arbitrary File Write
SNYK-JS-TAR-1579155
696 No Known Exploit
high severity Arbitrary File Overwrite
SNYK-JS-TAR-174125
696 Proof of Concept
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-SSRI-1246392
696 Proof of Concept
high severity Improper Verification of Cryptographic Signature
SNYK-JS-BROWSERIFYSIGN-6037026
696 No Known Exploit
medium severity Open Redirect
SNYK-JS-EXPRESS-6474509
696 No Known Exploit
medium severity Information Exposure
SNYK-JS-FOLLOWREDIRECTS-6444610
696 Proof of Concept
medium severity Time of Check Time of Use (TOCTOU)
npm:chownr:20180731
696 No Known Exploit
low severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-TAR-1536758
696 No Known Exploit
critical severity Incomplete List of Disallowed Inputs
SNYK-JS-BABELTRAVERSE-5962462
696 Proof of Concept
medium severity Prototype Pollution
SNYK-JS-MINIMIST-559764
696 Proof of Concept
medium severity Prototype Pollution
SNYK-JS-MINIMIST-559764
696 Proof of Concept
low severity Prototype Pollution
SNYK-JS-MINIMIST-2429795
696 Proof of Concept
low severity Prototype Pollution
SNYK-JS-MINIMIST-2429795
696 Proof of Concept
low severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-WORDWRAP-3149973
696 Proof of Concept
Release notes
Package name: redux
  • 4.2.1 - 2023-01-28

    This bugfix release removes the isMinified internal check to fix a compat issue with Expo. That check has added in early 2016, soon after Redux 3.0 was released, at a time when it was still less common to use bundlers with proper production build settings. Today that check is irrelevant, so we've removed it.

    What's Changed

    Full Changelog: v4.2.0...v4.2.1

  • 4.2.0 - 2022-04-18

    This release marks the original createStore API as @ deprecated to encourage users to migrate to Redux Toolkit, and adds a new legacy_createStore API as an alias without the deprecation warning.

    Goal

    Redux Toolkit (the @ reduxjs/toolkit package) is the right way for Redux users to write Redux code today:

    https://redux.js.org/introduction/why-rtk-is-redux-today

    Unfortunately, many tutorials are still showing legacy "hand-written" Redux patterns, which result in a much worse experience for users. New learners going through a bootcamp or an outdated Udemy course just follow the examples they're being shown, don't know that RTK is the better and recommended approach, and don't even think to look at our docs.

    Given that, the goal is to provide them with a visual indicator in their editor, like createStore . When users hover over the createStore import or function call, the doc tooltip recommends using configureStore from RTK instead, and points them to that docs page. We hope that new learners will see the strikethrough, read the tooltip, read the docs page, learn about RTK, and begin using it.

    To be extremely clear:

    WE ARE NOT GOING TO ACTUALLY REMOVE THE createStore API, AND ALL YOUR EXISTING CODE WILL STILL CONTINUE TO WORK AS-IS!

    We are just marking createStore as "deprecated":

    "the discouragement of use of some feature or practice, typically because it has been superseded or is no longer considered efficient or safe, without completely removing it or prohibiting its use"

    For additional details, see the extensive discussion in #4325 .

    Rationale

    • RTK provides a vastly improved Redux usage experience, with APIs that simplify standard usage patterns and eliminate common bugs like accidental mutations
    • We've had suggestions to merge all of RTK into the redux core package, or fully deprecate the entire redux package and rename it to @ reduxjs/core. Unfortunately, those bring up too many complexities:
      • We already had a package rename from redux-starter-kit to @ reduxjs/toolkit, and all of our docs and tutorials have pointed to it for the last three years. I don't want to put users through another whiplash package transition for no real benefit
      • Merging or rearranging our packages would effectively require merging all of the Redux repos into a single monorepo. That would require hundreds of hours of effort from us maintainers, including needing to somehow merge all of our docs sites together. We don't have the time to do that.
    • I don't want to add runtime warnings that would be really annoying

    So, this is the minimum possible approach we can take to reach out to users who otherwise would never know that they are following outdated patterns, while avoiding breaking running user code or having to completely rewrite our package and repo structure.

    Results

    When a user imports createStore in their editor, they will see a visual strikethrough. Hovering over it will show a doc tooltip that encourages them to use configureStore from RTK, and points to an explanatory docs page:

    image

    Again, no broken code, and no runtime warnings.

    If users do not want to see that strikethrough, they have three options:

    • Follow our suggestion to switch over to Redux Toolkit and configureStore
    • Do nothing. It's just a visual strikethrough, and it doesn't affect how your code behaves. Ignore it.
    • Switch to using the legacy_createStore API that is now exported, which is the exact same function but with no @ deprecation tag. The simplest option is to do an aliased import rename:

    image

    What's Changed

    • Mark createStore as deprecated, and add legacy_createStore alias by @ markerikson in #4336

    Full Changelog: v4.1.2...v4.2.0

  • 4.2.0-alpha.0 - 2021-10-30

    4.2.0-alpha.0

  • 4.1.2 - 2021-10-28

    This release fixes a small specific TS types issue where state types that had a nested unknown field inside would cause compilation failures when used as the preloadedState argument.

    What's Changed

    Full Changelog: v4.1.1...v4.1.2

  • 4.1.1 - 2021-08-03

    Just a small fix for Safari users in development mode.

    Changes

    • Move miniKindOf out of if scope to fix ES5 compatibility issue (#4090 by @ embeddedt)
from redux GitHub release notes
Package name: react-redux
  • 7.2.9 - 2022-09-23

    This patch release updates the rarely-used areStatesEqual option for connect to now pass through ownProps for additional use in determining which pieces of state to compare if desired.

    The new signature is:

    {
      areStatesEqual?: (
        nextState: State,
        prevState: State,
        nextOwnProps: TOwnProps,
        prevOwnProps: TOwnProps
      ) => boolean
    }

    What's Changed

    Full Changelog: v7.2.8...v7.2.9

  • 7.2.8 - 2022-04-01

    This release fixes a bug in the 7.x branch that caused <Provider> to unsubscribe and stop updating completely when used inside of React 18's <StrictMode>. The new "strict effects" behavior double-mounts components, and the subscription needed to be set up inside of a useLayoutEffect instead of a useMemo. This was previously fixed as part of v8 development, and we've backported it.

    Note: If you are now using React 18, we strongly recommend using the React-Redux v8 beta instead of v7.x!. v8 has been rewritten internally to work correctly with React 18's Concurrent Rendering capabilities. React-Redux v7 will run and generally work okay with existing code, but may have rendering issues if you start using Concurrent Rendering capabilities in your code.

    Now that React 18 is out, we plan to finalize React-Redux v8 and release it live within the next couple weeks. Per an update yesterday in the "v8 roadmap" thread, React-Redux v8 will be updated in the next couple days to ensure support for React 16.8+ as part of the next beta release. We would really appreciate final feedback on using React-Redux v8 beta with React 18 before we publish the final version.

    Full Changelog: v7.2.7...v7.2.8

  • 7.2.7 - 2022-03-31

    This release updates React-Redux v7's peer dependencies to accept React 18 as a valid version, only to avoid installation errors caused by NPM's "install all the peer deps and error if they don't match" behavior.

    Note: If you are now using React 18, we strongly recommend using the React-Redux v8 beta instead of v7.x!. v8 has been rewritten internally to work correctly with React 18's Concurrent Rendering capabilities. React-Redux v7 will run and generally work okay with existing code, but may have rendering issues if you start using Concurrent Rendering capabilities in your code.

    Now that React 18 is out, we plan to finalize React-Redux v8 and release it live within the next couple weeks. We would really appreciate final feedback on using React-Redux v8 beta with React 18 before we publish the final version.

  • 7.2.6 - 2021-10-25
  • 7.2.5 - 2021-09-04
from react-redux GitHub release notes
Package name: react-scripts
  • 2.1.8 - 2019-03-07
  • 2.1.7 - 2019-03-07
  • 2.1.6 - 2019-03-06
  • 2.1.5 - 2019-02-11
  • 2.1.4 - 2019-02-10
  • 2.1.3 - 2019-01-04
from react-scripts GitHub release notes
Package name: redux-thunk
  • 2.4.2 - 2022-11-04

    This release removes an unused TS type that caused errors when users were type-checking libraries in node_modules.

    What's Changed

    Full Changelog: v2.4.1...v2.4.2

  • 2.4.1 - 2021-11-26

    This release adds an explicit plain action overload to the ThunkDispatch TS type to better handle inference of the return value in some cases.

    What's Changed

    Full Changelog: v2.4.0...v2.4.1

  • 2.4.0 - 2021-10-26

    This very overdue release makes several major improvements to the TypeScript types, and converts the actual source to TypeScript. Sorry for the delay!

    Changelog

    TypeScript Improvements

    This release fixes several outstanding issues that had been reported with the types. An extra overload has been added to let TS correctly understand some generically-typed values being passed to dispatch, and the overloads have been reworked for additional compatibility.

    There's also a new ThunkActionDispatch type that can be used to represent how bindActionCreators turns bound thunks into (arg) => thunkReturnValue.

    Additionally, all of the generic args have been giving meaningful names instead of one-letter abbreviations (S -> State, E -> ExtraArgument, etc), and we've added descriptive comments in the type definitions for clarity.

    Optional Global Dispatch Type Extension

    Most Redux apps have the thunk middleware enabled, but the default Dispatch and bindActionCreator types only know about the standard behavior of a basic Redux store without any middleware. The thunk middleware types add to that type behavior, so that Dispatch knows dispatching a thunk can actually return a value such as a Promise.

    We generally recommend inferring the type of dispatch and using that to create reusable types, including creating pre-typed hooks. However, some users may prefer to globally augment the Dispatch type to always use the additional thunk behavior.

    You can now import 'redux-thunk/extend-redux' to globally augment the Dispatch type as an opt-in change in behavior.

    Codebase Converted to TypeScript

    We've gone ahead and converted the actual source to TS. Since the source was only 15-ish lines to begin with, most of the "conversion" time was just trying to convince TS that assigning thunk.extraArgument = createThunkMiddleware was a legal operation :)

    We also updated the build tooling:

    • Babel updates
    • Rollup for the UMDs instead of Webpack
    • Github Actions for CI instead of Travis

    Finally, the README has been updated with newer instructions and usage information.

    What's Changed

    New Contributors

    Full Changelog: v2.3.0...v2.4.0

  • 2.3.0 - 2018-05-28

    Hello! There's a new sheriff in town...

    This is only an update to the TypeScript typings for Redux 4.0 compatibility. After some discussion on the issues/PRs, we're going to be removing the typings completely in a 3.0 release soon. They will instead live in DefinitelyTyped, where they can be updated to match newer version of TypeScript and Redux at whatever pace they want to take. Farewell, typings! 🖖

from redux-thunk GitHub release notes
Package name: styled-components
  • 5.3.11 - 2023-05-26
  • 5.3.10 - 2023-04-23
  • 5.3.9 - 2023-03-13
  • 5.3.8 - 2023-03-02
  • 5.3.7 - 2023-03-02
  • 5.3.6 - 2022-09-27
  • 5.3.5 - 2022-03-24
  • 5.3.4 - 2022-03-24
  • 5.3.3 - 2021-10-19
  • 5.3.2 - 2021-10-19
  • 5.3.1 - 2021-08-24
from styled-components GitHub release notes
Package name: web3-eth-contract
  • 1.10.4 - 2024-02-05
  • 1.10.4-dev.0 - 2024-01-31
  • 1.10.3 - 2023-10-18
  • 1.10.3-dev.0 - 2023-10-16
  • 1.10.2 - 2023-08-28
  • 1.10.1 - 2023-08-14
  • 1.10.1-rc.0 - 2023-08-08
  • 1.10.0 - 2023-05-10
  • 1.10.0-rc.0 - 2023-05-02
  • 1.9.0 - 2023-03-20
  • 1.9.0-rc.0 - 2023-03-07
  • 1.8.2 - 2023-01-30
from web3-eth-contract GitHub release notes
Package name: web3
  • 1.10.4 - 2024-02-05
  • 1.10.4-dev.0 - 2024-01-31
  • 1.10.3 - 2023-10-18
  • 1.10.3-dev.0 - 2023-10-16
  • 1.10.2 - 2023-08-28
  • 1.10.1 - 2023-08-14
  • 1.10.1-rc.0 - 2023-08-08
  • 1.10.0 - 2023-05-10
  • 1.10.0-rc.0 - 2023-05-02
  • 1.9.0 - 2023-03-20...

Snyk has created this PR to upgrade:
  - redux from 4.1.1 to 4.2.1.
    See this package in npm: https://www.npmjs.com/package/redux
  - react-redux from 7.2.5 to 7.2.9.
    See this package in npm: https://www.npmjs.com/package/react-redux
  - react-scripts from 2.1.3 to 2.1.8.
    See this package in npm: https://www.npmjs.com/package/react-scripts
  - redux-thunk from 2.3.0 to 2.4.2.
    See this package in npm: https://www.npmjs.com/package/redux-thunk
  - styled-components from 5.3.1 to 5.3.11.
    See this package in npm: https://www.npmjs.com/package/styled-components
  - web3-eth-contract from 1.8.2 to 1.10.4.
    See this package in npm: https://www.npmjs.com/package/web3-eth-contract
  - web3 from 1.8.2 to 1.10.4.
    See this package in npm: https://www.npmjs.com/package/web3

See this project in Snyk:
https://app.snyk.io/org/debuggineffect/project/3434ae24-2c05-4389-8fa3-73e8544de373?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants