Skip to content

Telegram implementation#2

Open
andry2327 wants to merge 34 commits intomasterfrom
Telegram-implementation
Open

Telegram implementation#2
andry2327 wants to merge 34 commits intomasterfrom
Telegram-implementation

Conversation

@andry2327
Copy link
Copy Markdown
Owner

No description provided.

@gitguardian
Copy link
Copy Markdown

gitguardian Bot commented Jun 27, 2023

⚠️ GitGuardian has uncovered 9 secrets 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 secrets in your pull request
GitGuardian id Secret Commit Filename
- Generic High Entropy Secret 679b5a6 my_API_keys.py View secret
- Telegram Bot Token 679b5a6 my_API_keys.py View secret
- Generic High Entropy Secret d8a5ec7 my_API_keys.py View secret
- Telegram Bot Token d8a5ec7 my_API_keys.py View secret
4222420 Generic High Entropy Secret e9ebcd3 my_API_keys.py View secret
4222418 Telegram Bot Token e9ebcd3 my_API_keys.py View secret
4222419 Telegram Bot Token e9ebcd3 my_API_keys.py View secret
4222420 Generic High Entropy Secret 3d98898 my_API_keys.py View secret
4222419 Telegram Bot Token 3d98898 my_API_keys.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 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.

Our GitHub checks need improvements? Share your feedbacks!

Copy link
Copy Markdown
Owner Author

@andry2327 andry2327 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

branche merge

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.

1 participant