Repository navigation
Conversation
… manifest Auth validation exercises register/login/rejected inputs, bcrypt SQLite storage, JWT identity, and service restart without providers or mocks. Restore missing query container/packaging manifests and auth dependency declarations. Docker image build and live search remain unavailable in the current environment.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 38148924 | Triggered | Generic Password | d681dd5 | scripts/check_auth_http.py | 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 branch had an error being deployed
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
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.
The auth package omitted pydantic-settings and allowed bcrypt versions incompatible with its Passlib backend. The Compose query service pointed to an empty Dockerfile and packaging manifest.
Declare auth dependencies, add the actual query service build/run configuration, and add a repeatable provider-free HTTP persistence check with CI. It launches the existing auth application, registers an isolated account, checks duplicate and invalid registration, valid/invalid login and JWT identity, inspects bcrypt SQLite storage, restarts the process, and logs in again.
Validation: pip install --no-deps -e services/auth succeeds; python scripts/check_auth_http.py passes twice using real loopback HTTP and temporary SQLite, without service/provider mocks. git diff --check clean.
Scope: this proves local authentication only. No Docker CLI/socket exists in the execution environment, so query image build, Redis/OpenSearch search, browser agent and notify/ranker scaffolds remain unverified. Frontend repair #2 remains independent.