Fix Add GitLeaks to this repo with stage model

Original issue: #2

What is the feature

The feature is to integrate GitLeaks into the repository.

Why we need the feature

GitLeaks is a tool that helps in detecting and preventing secrets from being committed into the repository. Integrating GitLeaks will enhance the security of the project by ensuring that sensitive information such as API keys, passwords, and other secrets are not inadvertently exposed.

How to implement and why

Add GitLeaks to the project dependencies:
- Update the package.json file to include GitLeaks as a dependency. This ensures that GitLeaks is installed and can be run as part of the project's workflow.
Create a GitLeaks configuration file:
- Add a .gitleaks.toml configuration file to the root of the repository. This file will define the rules and patterns that GitLeaks will use to scan for secrets.
Update the .gitignore file:
- Ensure that the .gitignore file is configured to ignore any files or directories that should not be scanned by GitLeaks, such as build artifacts or other generated files.
Add a script to run GitLeaks:
- Update the package.json to include a script that runs GitLeaks. This script can be used to manually scan the repository for secrets.
Integrate GitLeaks into the CI/CD pipeline:
- Update the CI/CD configuration to run GitLeaks as part of the build process. This ensures that any new commits are automatically scanned for secrets before being merged.

By following these steps, we can ensure that GitLeaks is properly integrated into the project, providing an additional layer of security by preventing sensitive information from being committed to the repository.

Test these changes locally

git checkout -b stage/issue-#2-1c329642-f9ef-4053-af0a-b4d353612d61
git pull origin stage/issue-#2-1c329642-f9ef-4053-af0a-b4d353612d61

nikitamalinov / paulgrahamessays