Potential fix for code scanning alert no. 2: Clear-text logging of sensitive information#5
Merged
Code-lab-web merged 1 commit intomainfrom Feb 16, 2026
Merged
Conversation
…nsitive information Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
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.
Potential fix for https://github.com/Code-lab-web/project-final/security/code-scanning/2
In general, the fix is to avoid logging sensitive fields (like passwords) at all. If logging is needed for debugging, either remove it or log only non-sensitive metadata (for example, just the email or a static message indicating a submission occurred). The change should not alter functional behavior of the signup process, only its logging.
The best minimal fix here is to replace
console.log(formData);with a log statement that does not include the password. For example, log just the email or a generic message:console.log("Signup form submitted for email:", formData.email);. This keeps some visibility for debugging without exposing the password. No imports or additional helpers are needed; we only change the single logging line infrontend/components/pages/SignupForm.jsx. All other behavior, including thefetchcall and form resetting, remains unchanged.Suggested fixes powered by Copilot Autofix. Review carefully before merging.