Module sport results

[BLEMENT33]

Description

Made a module to show sport results of all the sport teams to Centraliens

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 14 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
7298663	Triggered	RSA Private Key	4c1e54d2fdca16bc2bf4e565e9a2198152da6327	.env.test	View secret
7298663	Triggered	RSA Private Key	c6e0413c3bbaa907c5b09709c632423eac371e09	.env.test	View secret
7298664	Triggered	Generic Password	4c1e54d2fdca16bc2bf4e565e9a2198152da6327	tests/test_auth.py	View secret
7298664	Triggered	Generic Password	4c1e54d2fdca16bc2bf4e565e9a2198152da6327	tests/test_auth.py	View secret
7298664	Triggered	Generic Password	4c1e54d2fdca16bc2bf4e565e9a2198152da6327	tests/test_auth.py	View secret
7298664	Triggered	Generic Password	4c1e54d2fdca16bc2bf4e565e9a2198152da6327	tests/test_auth.py	View secret
7298664	Triggered	Generic Password	4c1e54d2fdca16bc2bf4e565e9a2198152da6327	tests/test_auth.py	View secret
7298664	Triggered	Generic Password	4c1e54d2fdca16bc2bf4e565e9a2198152da6327	tests/test_auth.py	View secret
7298664	Triggered	Generic Password	4c1e54d2fdca16bc2bf4e565e9a2198152da6327	tests/test_auth.py	View secret
7298664	Triggered	Generic Password	4c1e54d2fdca16bc2bf4e565e9a2198152da6327	tests/test_auth.py	View secret
7298664	Triggered	Generic Password	c6e0413c3bbaa907c5b09709c632423eac371e09	tests/test_auth.py	View secret
7298664	Triggered	Generic Password	5c9118aab54587f656631e8cc1ebeb1f6050c404	tests/test_auth.py	View secret
7298668	Triggered	Generic High Entropy Secret	4c1e54d2fdca16bc2bf4e565e9a2198152da6327	.env.test	View secret
7298668	Triggered	Generic High Entropy Secret	c6e0413c3bbaa907c5b09709c632423eac371e09	.env.test	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.

---

^{🦉 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.}