Skip to content
This repository has been archived by the owner on Oct 18, 2023. It is now read-only.

BytesToBits/LockPass

Repository files navigation

LOCKPASS, A PASSWORD MANAGER

LockPass

LockPass is a simple passsword manager made using Electron + Next.js (Nextron).

How it works

  • Head over to the Releases tab and download the latest version. The file you must download must be formatted like so: LockPass-Setup-[VERSION].exe
  • Run the downloaded file. Chrome and Windows might try to prevent its download, but you can discard the alerts if you wish. There are no threats in the applications whatsoever.
  • Whenever there is a new release, the application will update automatically.
  • Passwords are saved locally, so there is no fear of having them leaked online.

To-Do (v1.6.0 -> v2.0.0)

  • Improve Home Design
  • Improve Password Preview Design
  • A more protective way of storing passwords (encryptions & user pin)
  • More customization settings
  • Organize/Clean code files
  • Add an accounts feature to store passwords online
  • Bin (Tab to see & be able to restore old passwords within 30 days of deletion)

Contributions

All contributions are welcome! Feel free to work on any of the above To-Do features. Make sure, however, that your commit messages follow the guidelines below to make it easier for us to track. it's fine if you don't

  1. Select the type of commit:
    feat: The new feature you're adding to a particular application
    fix: A bug fix
    style: Feature and updates related to styling
    refactor: Refactoring a specific section of the codebase
    test: Everything related to testing
    docs: Everything related to documentation
    chore: Regular code maintenance.[ You can also use emojis to represent commit types]
  2. Separate the subject from the body with a blank line
  3. Your commit message should not contain any whitespace errors
  4. Remove unnecessary punctuation marks
  5. Do not end the subject line with a period
  6. Capitalize the subject line and each paragraph
  7. Use the imperative mood in the subject line
  8. Use the body to explain what changes you have made and why you made them.
  9. Do not assume the reviewer understands what the original problem was, ensure you add it.
  10. Do not think your code is self-explanatory

Read this article to learn more

Once you are done with your contribution, create a Pull Request!

💖 CONTRIBUTORS 💖