Skip to content

Conversation

@CarterPerez-dev
Copy link
Owner

Description

Provide a clear description of what this pull request does.

Type of Change

  • New project idea (SYNOPSES)
  • [x ] Full project implementation
  • Bug fix
  • Documentation improvement
  • Other (please describe)

Checklist

  • My code follows the existing style and conventions
  • I have tested my changes
  • I have updated relevant documentation - TODO: - [ ]
  • My changes do not introduce security vulnerabilities
  • I have read the CONTRIBUTING.md guidelines

Related Issues

Link any related issues here (e.g., "Fixes #123").

Additional Context

Any other information that reviewers should know.

@gitguardian
Copy link

gitguardian bot commented Nov 28, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
22931432 Triggered Generic High Entropy Secret 7f324ef PROJECTS/encrypted-p2p-chat/backend/tests/conftest.py 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.

@github-actions
Copy link

🔍 Lint & Type Check Results

✅ Pylint: Passed

No pylint issues found.

✅ Ruff: Passed

No ruff issues found.

✅ Mypy: Passed

No mypy issues found.


All checks passed!

@CarterPerez-dev CarterPerez-dev merged commit ce4a459 into main Nov 28, 2025
2 checks passed
@github-actions
Copy link

🔍 Lint & Type Check Results

✅ Pylint: Passed

No pylint issues found.

✅ Ruff: Passed

No ruff issues found.

✅ Mypy: Passed

No mypy issues found.


All checks passed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants