Awesome
<div align="center"> <img src="./src/assets/icons/logo.svg" width="250" height="250"/> </div> <br />Passwords Fountain
Modern & performant password manager interface which works everywhere :iphone: :computer: :tv:
Passwords Fountain is completely free and lightweight UI. Start your journey* at https://www.passwords-fountain.com
*Note: To start, you don't have to host / own anything but your browser
<div align="center"> <img src="./src/assets/images/how-it-works-readme.png" width="350" /> </div>Sounds great! How to start?
There is 5-step mini guide on our Homepage, check it out: https://www.passwords-fountain.com
If you feel that you need additional help to setup the app, don't hestitate to contact with the author: https://twitter.com/kolodziejczakMn
Is it safe?
We do our best to make it safe:
- We don't store any vulnerable data - your passwords neither land on localStorage, sessionStorage, IndexedDB nor any server.
- Passwords Fountain has access to your database as long as you want to. You can remove admin key from your database account anytime (it's you who are in control!).
- In your database (https://fauna.com/) passwords are stored in encrypted version so nobody can steal them from there.
- We use strict Content-Security-Policy to prevent any third party script from being injected during application runtime.
- We don't use any tracking / logging tool like: Google Analytics, LogRocket or Sentry.
- Whole application flow is public and you can see it here: Figma
- We released a newsletter to provide you with latest news about the application state.
What you can do to make it safe:
- Don't give your FaunaDB admin key* to anybody. If somebody intercepts it they may be able to delete your passwords or add anything to your database.
- Be careful when decrypting your passwords in public - they may be noticed by people around you.
*FaunaDB admin key is a database token needed to establish connection between FaunaDB (database) and Passwords fountain (user interface).
What can make you feel safe?
- You can always check in what way Passwords Fountain works via putting "random" data into it - you don't risk anything. Again - it's the best to start from our 5-step mini guide which you can find here.
- If you're a programmer - you can even go through application code to ensure that your privacy is not violated. If you still don't feel save, then maybe try running your own instance?
Can I run my own instance?
Of course! If you don't want to use official Passwords Fountain instance from https://www.passwords-fountain.com, you can fork the code, use any (free?) static site hosting service and you are all set!
Using "public" instance is preferred though - we can polish it together. It can be hard to help with bug fixing on your private, modified instance.
I found a bug. What should I do?
Don't hesitate to open an issue! If you're new on github, read this guide.
I opened an issue, but I also want to help in closing them. Can I?
Of course! Contribution flow looks like this:
- Fork this repo
- Create your feature branch (
git checkout -b new-feature
) on your fork. - Write the code.
- Write tests!
- Commit your changes via
npm run commit
- we use commitizen to ensure that all commits will have appropriate structure. - Push to your origin branch via
npm run push
- this will bump code version inpackage.json
andpackage-lock.json
files, updateCHANGELOG.md
and create git tag. - Create new pull request (from
your_fork_repository/new-feature
to this repository master branch). - Wait for code review and react accordingly, thanks a lot!
Contact
Don't hestitate to ask questions I'm always willing to help - https://twitter.com/kolodziejczakMn