Conversation
…face directory and subdirectories
* Add relevant environment variable to ENV.md * Fix bug in manual DeepSeekRecordClassifier test * Update DeepSeekRecordClassifier.py to pass test * Refine URLHTMLContentInfo to include list of strings
* Refine Task Operators to follow unified logic, including logging * Add tables related to tracking tasks and errors/urls within tasks * Add new tests, update and refine existing tests * Refactor some database client logic
…ord_category_labeling Mc record category labeling
…_pyproject_toml Convert to full uv/pyproject dependency management
…_pyproject_toml mc_261_pyproject_toml
…_metrics_endpoints mc_125_metrics_endpoints
Previously, agency identification was erroneously pulling up URLs that had an error status. This has been addressed.
Previously, agency identification was erroneously pulling up URLs that had an error status. This has been addressed.
…_relevancy_task_error fix(app): Address bug in agency identification
…_duplicate_check_task feat(app): add url duplicate check task operator
…_pdap_access_manager feat(app): replace in-project access manager with `pdap_access_manager`
…_pdap_access_manager feat(app): Change metrics endpoints from per week to per month
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 16713553 | Triggered | Generic Password | 72ed9c9 | local_database/setup_fdw.sh | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.