meliorence / meliorence/react-native-snap-carousel

npm audit fix - downgrade this package version to 1.3.1

Open
#828 4 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
10.5k
Forks
2.3k
PR merge metrics
No merged PRs in 30d

Description

React Native Version - 0.64.0

@react-native-community/cli - 5.0.1-alpha.2
"react-native-snap-carousel": "^3.9.1",

When I hit npm audit I got the following response

# npm audit report

node-fetch  <=2.6.0 || 3.0.0-beta.1 - 3.0.0-beta.8
Denial of Service - https://npmjs.com/advisories/1556
fix available via `npm audit fix --force`
Will install react-native-snap-carousel@1.3.1, which is a breaking change
node_modules/isomorphic-fetch/node_modules/node-fetch
  isomorphic-fetch  2.0.0 - 2.2.1
  Depends on vulnerable versions of node-fetch
  node_modules/isomorphic-fetch
    fbjs  0.7.0 - 1.0.0
    Depends on vulnerable versions of isomorphic-fetch
    node_modules/react-addons-shallow-compare/node_modules/fbjs
      react-addons-shallow-compare  15.4.2 - 15.6.2 || >=16.0.0-alpha
      Depends on vulnerable versions of fbjs
      node_modules/react-addons-shallow-compare
        react-native-snap-carousel  >=1.4.0
        Depends on vulnerable versions of react-addons-shallow-compare
        node_modules/react-native-snap-carousel

5 low severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

I wonder why the npm audit asks me to downgrade the package version.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing npm audit with React Native 0.64.0, react-native-snap-carousel 3.9.1, and the listed CLI version. Trace the dependency chain through react-addons-shallow-compare, fbjs, isomorphic-fetch, and node-fetch; done means documenting why npm selects 1.3.1 and whether a supported non-breaking resolution exists.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react-native
Domain
mobile, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.