Ulkuw1

[ATLAMAZ]

Feature/Change Description

Describe changes made here, link to any issue that is addressed

Developer Checklist

• [ ] Updated documentation or README.md
• [ ] If adding new feature(s), added and ran unit tests
• [ ] If create new release, bumped version number
• [ ] Ran npm run style:fix for code style enforcement
• [ ] Ran npm run lint:fix for linting
• [ ] Ran npm audit to discover vulnerabilities

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-		OpenWeatherMap Token	dfb6d52d163260c123b815972c6c70e30c9e1274	cypress/e2e/boston.cy.ts	View secret
-		OpenWeatherMap Token	36d6ffe716defc1a0982844e1b59fde3d475befc	cypress/e2e/zipcode.cy.ts	View secret
-		OpenWeatherMap Token	63194cc32908a3b86590e0f504badb5dd0c75375	cypress/e2e/boston2.cy.ts	View secret
-		OpenWeatherMap Token	6349b1001282e80bca46b39e90b9ee48c159fc73	cypress/e2e/boston.cy.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[duluca]

Closing because PR is unactionable.