Pensar - auto fix for Exposed Environment File with Hard-coded Credentials in Version Control

[pensarappdev]

• The .gitignore entry for .env is kept, and new patterns are added: .env.* ignores all environment-specific/variant or backup files; !.env.example explicitly allows version-controlled example env files for documentation/onboarding purposes.
• Existing comments are clarified: the purpose of ignoring is now stated directly regarding secrets, and the section for IDE/editor files is labeled.
• No application code or dependency configuration required changes.

More Details

Type	Identifier	Message	Severity	Link
Application	CWE-798	The presence of a .env file checked into the repository strongly indicates that Twitter API keys and other sensitive credentials are stored in plaintext within source control. This constitutes hard-coded / exposed credentials (CWE-798). Anyone with read access to the repository could harvest these secrets, impersonate users, or abuse the Twitter API on their behalf. Secrets should never be committed to version control; instead, they should be injected at runtime via a secure secrets-management system.	critical	Link