COS301-SE-2024 / Events-System

Our team brings you an innovative team collaboration site powered by angular, structured and managed by NX
3 stars 1 forks source link

Post demo update #173

Closed Mathenda closed 1 month ago

Mathenda commented 1 month ago

Pull Request

Description:

[Provide a concise summary of your changes and why they are necessary.]

Related Issues:

[Reference any related issues or documents.]

Type of Change:

Checklist:

Reviewers:

Testing Instructions:

[Provide clear and concise instructions on how to test your changes.]

Screenshots (if applicable):

[Add screenshots to help reviewers understand the changes visually.]

Additional Notes:

[Any additional information that may be helpful for reviewers.]

gitguardian[bot] commented 1 month ago

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [11421788](https://dashboard.gitguardian.com/workspace/301252/incidents/11421788?occurrence=162886210) | Triggered | Generic High Entropy Secret | bf827e02cdf0e29d7a84651dcb1eb64f05bf7976 | Backend/src/main/resources/application.properties | [View secret](https://github.com/COS301-SE-2024/Events-System/commit/bf827e02cdf0e29d7a84651dcb1eb64f05bf7976#diff-620b0ae7dd60ab859ff2019f38f1353b9ff311a228b4a9dd06215f99dec88c25L14) |
🛠 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 secret safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/generic_high_entropy_secret#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) 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.

codecov[bot] commented 1 month ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 43.45%. Comparing base (d18932c) to head (9c3385e). Report is 33 commits behind head on develop.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## develop #173 +/- ## =========================================== + Coverage 43.19% 43.45% +0.26% =========================================== Files 71 72 +1 Lines 213 214 +1 Branches 8 8 =========================================== + Hits 92 93 +1 Misses 121 121 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.