forked from jbarrow/commonforms
-
Notifications
You must be signed in to change notification settings - Fork 0
π‘οΈ Sentinel: [CRITICAL] Fix hardcoded test password #16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
kingkillery
wants to merge
1
commit into
main
Choose a base branch
from
sentinel-fix-hardcoded-test-password-2212744582073882906
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| ## 2025-04-12 - Critical: Avoid Hardcoded Credentials in Test Comments | ||
|
|
||
| **Vulnerability:** A hardcoded password ("kanbanery") for an encrypted PDF file was found in a comment within `tests/inference_test.py`. | ||
| **Learning:** Comments in test files can inadvertently leak sensitive information, such as passwords used for test resources. Hardcoded secrets, even when intended purely for internal or test use, can pose a risk if the repository is ever compromised or exposed. | ||
| **Prevention:** Never include passwords or other sensitive secrets in the codebase, including in code comments or test scripts. If passwords are required for testing, they should be managed via environment variables or a secure secret manager, and test resources should ideally use widely known, non-sensitive credentials (e.g., "password123") if they must be embedded. | ||
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct the date to match the PR creation date.
The date shows "2025-04-12" but the PR was created on "2026-04-12". This appears to be a typo.
π Proposed fix
π Committable suggestion
π€ Prompt for AI Agents