Joel dev2

[Shan-Joel]

No description provided.

[gitguardian]

⚠️ GitGuardian has uncovered 16 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	Secret	Commit	Filename
7298826	Google API Key	4489812	backend/ml_models/recommanded_system/youtube_search.py	View secret
7298826	Google API Key	4489812	backend/ml_models/recommanded_system/youtube_search.py	View secret
7412028	OpenAI API Key	4489812	backend/ml_models/emotion_detection/emotionScript.py	View secret
7412028	OpenAI API Key	4489812	backend/ml_models/emotion_detection/emotionDetection.ipynb	View secret
7606532	OpenAI API Key	4489812	backend/ml_models/emotion_detection/emotionDetection.ipynb	View secret
8008536	Spotify Keys	81345ff	frontend/src/pages/MusicTherapy.js	View secret
8008536	Spotify Keys	3aee9bd	frontend/src/pages/MusicTherapy.js	View secret
8429691	OpenAI API Key	4489812	backend/ml_models/Chatbot/chatbotkb.py	View secret
8587996	OpenAI API Key	4489812	backend/ml_models/emotion_detection/emotionScript.py	View secret
8599200	OpenAI API Key	4489812	backend/ml_models/Chatbot/chatbotkb.py	View secret
8603310	Generic High Entropy Secret	4489812	backend/ml_models/spotify_recommendation/.cache	View secret
8603617	Generic High Entropy Secret	4489812	backend/ml_models/spotify_recommendation/.cache	View secret
8603618	Generic High Entropy Secret	4489812	backend/.cache	View secret
8603619	Generic High Entropy Secret	4489812	backend/ml_models/spotify_recommendation/.cache	View secret
8605705	OpenAI API Key	4489812	backend/ml_models/emotion_detection/emotionDetection.ipynb	View secret
8605705	OpenAI API Key	4489812	backend/ml_models/Chatbot/ChatbotKB.ipynb	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>