fix: Hardcoded credentials in seed script#48
Open
mrwind-up-bird wants to merge 1 commit intomainfrom
Open
Conversation
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.
AutoFix: Hardcoded credentials in seed script
Category: security
Severity: medium
Issue
The admin seeding script contains a hardcoded email address and password. This creates a predictable admin account that could be exploited if the script is run in production environments.
Fix
Replaced hardcoded admin credentials with environment variables (ADMIN_EMAIL and ADMIN_PASSWORD) that have safe defaults. This prevents predictable admin accounts in production while maintaining functionality for development environments.
Generated by nyxCore AutoFix