Skip to content

feat(backend): WebSocket relay retry and telemetry, payment processor telemetry suites, log retention validation - #1602

Open
noevidence1017 wants to merge 1 commit into
emdevelopa:mainfrom
noevidence1017:feature/be-websocket-relay-retry-telemetry-log-retention-validation
Open

noevidence1017 wants to merge 1 commit into
emdevelopa:mainfrom
noevidence1017:feature/be-websocket-relay-retry-telemetry-log-retention-validation

feat(backend): add websocket relay retry and telemetry, payment proce…

a5a3939
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks failed Oct 16, 2026 in 32s

1 secret uncovered!

1 secret was uncovered from the scan of 1 commit 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 #1602: feature/be-websocket-relay-retry-telemetry-log-retention-validation 👉 main
GitGuardian id GitGuardian status Secret Commit Filename
- - Generic High Entropy Secret a5a3939 backend/src/lib/websocket-relay-retry.test.js 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 secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  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.