Move react-native-sensitive-info to react-native-community

[pererasys]

Introduction

I'm not sure how this works as I'm not the developer of this library, but I think it should be considered as an addition to react-native-community.

Repo:
https://github.com/mCodex/react-native-sensitive-info

Author:
@mCodex

Details

This was talked about in an issue on its github repo (mCodex/react-native-sensitive-info#181), but this is a great library that should be more popular than it is, and the current developer apparently stated he no longer has time to maintain.

Discussion points

In my opinion, this is the current best option for handling sensitive information and a lot of people will likely have to resort to encrypted databases or device-specific solutions if it goes unmaintained.

It's possible a lot of people are unaware async storage shouldn't be used for sensitive information, and by moving to RNC the issue may attract more attention.

[mCodex]

RNSensitiveInfo was created in 2016 to solve one problem that I was having back then. However, a lot have changed since then and I know there are a lot of projects depending on it but I don't have enough time to dedicate myself to this project and also not having the necessary knowledge in native code to implement new features.

In the past few years, the community has been helping me opening pull requests (I'm so thankful for all of them <3) and I was merging/releasing new versions. We recently reached 12k+ downloads per week.

If anyone from the community would like to take over this project, please let me know.

[brentvatne]

First off, congrats on the success of your project @mCodex!

this is a great library that should be more popular than it is, and the current developer apparently stated he no longer has time to maintain.

Personally, I don't think this organization should become a place that libraries are placed because they are no longer actively maintained or because they would like to have more publicity.

It's possible a lot of people are unaware async storage shouldn't be used for sensitive information, and by moving to RNC the issue may attract more attention.

Moving a package to this org isn't how we should be documenting such knowledge. In this case, we should probably be adding more information to the AsyncStorage documentation and point people to https://reactnative.directory to find a library better suited to handle their needs. By doing so, devlopers can discover the available options:

• rn-secure-storage
• expo-secure-store
• react-native-keychain
• react-native-sensitive-info

Developers can then use the information presented on that website or in the project READMEs to determine which is best for them.

[mCodex]

@brentvatne thanks for your response. It meant a lot! I've been following your work since I started studying RN back to January of 2016. I really appreciated your words, so I decided to keep working on this awesome library that I and the awesome community has been built so far.

I hope RNSensitiveInfo can be part of react-native-community due to our work and not as you said only for being no longer actively maintained.

Feel free to close this issue for now 😄