-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 4.0.1 #411
Release 4.0.1 #411
Conversation
Feat/nav bar fixed
…entsColors Feat/define fine tune components colors
…n links to buttons and use router navigate
-Coverage at 80.42% -Moving on to Frontend test fixing
…entsColors Updated Login and Register colors and styling
Feat/mobile interface
Feat/minor fixes
📐Refactor big-rounded-square-card component added mouseLeave event
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To main!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stinkies
Stablization
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
13964749 | Triggered | Generic Password | 0c1a641 | Frontend/src/app/components/templates/desktop/desk-register/desk-register.component.spec.ts | View secret |
13964749 | Triggered | Generic Password | 0c1a641 | Frontend/src/app/components/templates/desktop/desk-register/desk-register.component.spec.ts | View secret |
13964749 | Triggered | Generic Password | 1cba122 | Frontend/src/app/components/templates/desktop/desk-register/desk-register.component.spec.ts | View secret |
13964749 | Triggered | Generic Password | 1cba122 | Frontend/src/app/components/templates/desktop/desk-register/desk-register.component.spec.ts | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- 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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Red Cross reigns supreme
No description provided.