DependencyCheck VS react-native-firebase

Use Security Tools: To identify known vulnerabilities in your project's dependencies, you can utilize commands like npm audit or employ third-party security scanners such as DependencyCheck or Dependabot. These tools thoroughly analyze the dependency tree and offer actionable insights to assist you in resolving any identified vulnerabilities.

OWASP DependencyCheck - a really decent tool for scanning your project for vulnerable dependencies. It is actively developed and updated and up to date with the most latest vulnerabilities. Sometimes it can be a pain in the ass, though. Some security researchers and such find a vulnerability, publish it and the next day our CI/CD pipelines fail (the dependency check build step prevents the code from going to production). And not always there is a fix available. So, some vulnerabilities have to be ignored, temporarily. Also, to be able to ignore a vulnerability one has to do a fast risk assessment. And that will require from him to read about the vulnerability and decide if it is safe to be ignored or some different workaround must be found.

The ultimate guide somehow fails to mention the best CVE checker: https://github.com/jeremylong/DependencyCheck

We run https://github.com/jeremylong/DependencyCheck over our dependency tree regularly, via this Clojure wrapper: https://github.com/clj-holmes/clj-watson which tells us the dependency tree path to each item that has a CVE and also the version in which the CVE is addressed, if known.

We use OWASP dependency-check and pass reports to SonarQube.

From OWASP for those class of tools you could look into DependencyCheck and DependencyTrack

DependencyCheck is an open source tool that checks for vulnerabilities in dependencies used within a project. While it is a reactive tool, it's an important one since the code a developer writes is not the only code an application uses.

One more aspect to consider, although I know it is not the primary ask of the post, is to be sure and run something like dependency check on your repository. There are quite a few vulnerabilities being injected through the packaging process these days.

We'll be utilizing React Native Firebase for this.

I used Expo-React native so I didn't use directly rnfirebase.io.

I found someone who had a similar issue: https://github.com/invertase/react-native-firebase/issues/1317

Otherwise, if you want remote storage a many other useful backend capabilities without writing and maintaining your own backend (messaging, remote updates, etc.) you can use Firebase. This is a very useful suite of tools from google that lots of people use that can handle Social Authentication, Push Notifications, Analytics, A few different kinds of data bases with both local and remote persistence. You won't need this for your todo but you might want to use it if you're making something more serious.

I’m following the exact same instructions as found here [https://rnfirebase.io/] but once I’m done with all the steps and build my project again, I get a very very long error that even my VS Code zsh terminal just cuts off.

Just add the code it does all I’m using https://rnfirebase.io/ if expo does support firebase it might work the same, use expo docs instead..

For firebase analytics just check out https://rnfirebase.io/ and read their documentation. It works for me! Also don‘t forget to build a custom dev client with eas.

If it is a bare RN application, make sure to follow the steps here to set up the SDK. Once you have set up the SDK, you need to set up all other services you are using on Firebase. For example, if you’re using Firestore, go to the Firestore usage docs and set it up.