Skip to content

Conversation

@aziz-ullah-khan
Copy link
Contributor

With Google Search, the issue was of too many request if the google search was hit frequently. In the google package, don't have proxy, so replace that with googlesearch-python, and integrated the proxy.

@gitguardian
Copy link

gitguardian bot commented Oct 11, 2024

⚠️ GitGuardian has uncovered 4 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.

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.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
- - Basic Auth String e828c70 notebook.ipynb View secret
- - Basic Auth String 46195d6 notebook.ipynb View secret
- - Username Password 46195d6 notebook.ipynb View secret
- - Username Password e828c70 notebook.ipynb 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.

@VinciGit00 VinciGit00 merged commit 0a275d5 into ScrapeGraphAI:pre/beta Oct 11, 2024
@github-actions
Copy link

🎉 This PR is included in version 1.26.0-beta.16 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 This PR is included in version 1.26.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants