manishkumar8312 / manishkumar8312/QuickStay
.env file not ignored — potential security risk
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
I noticed that the .env file is not included in the .gitignore. Since .env files often contain sensitive information like API keys or database credentials, it's best practice to exclude them from version control to prevent accidental exposure.
I recommend adding .env to the .gitignore.
@manishkumar8312 I would like to take up this issue under GSSoC'25. Please assign me this issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the repository's .gitignore and check whether .env is already covered by an existing pattern. Add the requested entry if it is missing, then verify that a local .env file is ignored by Git. Done means the ignore rule is present and the file does not appear as an untracked candidate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- security
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100