Vulnerabilities in Package
@Kathuria is already working on this.
Since Oct 24, 2025.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- react-native, typescript
- Domain
- mobile-dev, security
Research direction
Start by installing version 1.0.0 with npm and auditing the dependency tree to identify which packages produce the 18 reported vulnerabilities. Confirm whether the findings affect runtime dependencies, then define done as resolving the applicable vulnerabilities without breaking the React Native SDK.
Written by the indexing model from the issue text.
Description
Bug report for Cloudinary React Native SDK
Before proceeding, please update to latest version and test if the issue persists
Describe the bug in a sentence or two.
During install process, npm says there are 18 vulnerabilities (14 moderate, 4 high). It installs just fine, but I am a little less than thrilled to be adding it to my project.
Issue Type (Can be multiple)
[ ] Build - Can’t install or import the SDK
[ ] Performance - Performance issues
[ ] Behaviour - Functions aren’t working as expected (Such as generate URL)
[ ] Documentation - Inconsistency between the docs and behaviour
[x] Other (Specify) - Security
Steps to reproduce
Install package using npm
Error screenshots or Stack Trace (if applicable)
Build/Dependency management
[x] Cocoa-Pods
[ ] Carthage
[ ] Manual import
[x] Other (Specify) - npm
Is the issue reproducible only on a specific device?
[x] No - not tested, but given the circumstances, I wouldn't think so
[ ] Yes (specify device model + iOS/Android version)
Versions and Libraries (fill in the version numbers)
React Native Cloudinary SDK version - 1.0.0
OSX (on the dev environment) - 14.5
Repository
If possible, please provide a link to a reproducible repository that showcases the problem
- Dominant language
- TypeScript
- Stars
- 28
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudinary/cloudinary-react-native
-
hacktoberfest-accepted
Difficulty 3/5 1-2 days Newbie friendliness 45/100
cloudinary/cloudinary-react-native#55 · 3 comments ·
-
Add CODE_OF_CONDUCT.mdMay be free again @adimiz1 claimed this 406 days ago, and no pull request is open. Open
cloudinary/cloudinary-react-native#53 · 2 comments · 1 assignee ·
-
Support for expo 54Open
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
cloudinary/cloudinary-react-native#52 · 8 comments ·
-
Issue: Improve `bootstrap.js` to support both Yarn and NPM with clearer errorsPossibly taken @adimiz1 claimed this 415 days ago. Open
cloudinary/cloudinary-react-native#50 · 3 comments · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
All issues in cloudinary/cloudinary-react-native
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug platform-android
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Termix-SSH/Mobile#146 · 1 comment ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
devswha/herdr-web-ui#3875 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
area: runtime chore cli consistency dependencies developer-experience difficulty: easy discovery documentation enhancement good first issue help wanted hygiene json-output packaging priority: P3 tests version
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day