Pensar - auto fix for Environment File Exposure in Source Control

[pensarappdev]

• The .gitignore was updated to:
  • Expand the exclusion to cover all environment and secret files via .env.*, while explicitly allowing .env.example in case a template/example is provided.
  • Added a comment block warning about the necessity to rotate credentials and scrub history if the sensitive files were previously committed, and linked to official documentation.
  • Ensured .env (single and patterns) are robustly ignored to prevent future credential leaks.
• No code changes outside .gitignore were made, as per instruction and relevance to the identified issue.

More Details

Type	Identifier	Message	Severity	Link
Application	CWE-798	The project includes a .env file in the repository. These files typically contain plaintext credentials (e.g., Twitter API keys). Committing them to source control exposes secrets to anyone with repository access or via public history leaks, enabling unauthorized use of the Twitter API, account takeover, or further pivot attacks.	high	Link