Skip to content

Resolved merge conflicts, kept local changes

af93ad4
Select commit
Loading
Failed to load commit list.
Merged

Implemented Payment History Table #7

Resolved merge conflicts, kept local changes
af93ad4
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks failed Feb 13, 2026 in 32s

6 secrets uncovered!

6 secrets were uncovered from the scan of 3 commits in your pull request. ❌

Please have a look to GitGuardian findings and remediate in order to secure your code.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

Details

πŸ”Ž Detected hardcoded secrets in your pull request

  • Pull request #7: main πŸ‘‰ main
GitGuardian id GitGuardian status Secret Commit Filename
24024965 Triggered Generic Password 4ff6ff2 services/mockApi.ts View secret
24024968 Triggered Generic Password 4ff6ff2 services/mockApi.ts View secret
24024969 Triggered Generic Password 4ff6ff2 services/mockApi.ts View secret
24024970 Triggered Username Password 4ff6ff2 services/mockApi.ts View secret
24024971 Triggered Generic Password 4ff6ff2 services/mockApi.ts View secret
24024972 Triggered Generic Password 4ff6ff2 services/mockApi.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


πŸ¦‰ 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.