🔎 Detected hardcoded secrets in your pull request

• Pull request #6210: codecanvas-diagram-1759529879489 👉 main

🛠 Guidelines to remediate hardcoded secrets

A potential secret has been detected in this pull request. Please take the following steps immediately:

1. Triage the Finding - Determine if the finding is a True Positive (a real secret) or a False Positive (e.g., test data, an example key).
   • For more triage information, click on the hyperlinked GitGuardian ID in the table above. You can also use these docs as a triage guide.
     • If this is a True Positive, proceed to step 2.
     • If it's a False Positive, follow the guide to handle false positives instead. If you're a team leader, click on the Remediation tab in GitGuardian to view the ignore approval request.

Not your repo? Get access to the GitGuardian issue by following these steps.

2. Start an Incident

   • If this is a True Positive, immediately declare a security incident. Do not merge this pull request.
     1. In Slack, type /fh and press Enter.
     2. Click the "🔥Open Incident" button.
     3. Select "Security Incident" from the "Incident Type" dropdown menu.

3. Follow the Runbook

   • The complete response procedure is documented in the runbook.

Have questions? Contact your ProdSec partner or post in #ask-prodsec.

🦉 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.