Skip to content

jj - #10

Open
dsactivi-2 wants to merge 151 commits into
devshift-stack:mainfrom
dsactivi-2:main
Open

jj#10
dsactivi-2 wants to merge 151 commits into
devshift-stack:mainfrom
dsactivi-2:main

docs: Add cloud agent installation documentation (#33)

40b10c4
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks failed Feb 16, 2026 in 56s

3 secrets uncovered!

3 secrets were uncovered from the scan of 151 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 #10: main 👉 main
GitGuardian id GitGuardian status Secret Commit Filename
- - Company Email Password 1b6c78c send-access-email.js View secret
- - Generic Password 1de297d tests/password-hashing.test.ts View secret
23405797 Triggered Generic Password 963b819 tests/auth-improvements.test.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.