Skip to content

Security: TejasS1233/en-git

Security

.github/SECURITY.md

πŸ›‘οΈ Security Policy

πŸ”„ Supported Versions

Version Supported
main βœ… Supported
dev πŸ§ͺ Under Testing
old / archived branches ❌ Not Supported

🚨 Reporting a Vulnerability

If you discover a security issue or potential vulnerability in en-git, please do not open a public GitHub issue.
Instead, report it privately using one of the methods below:

  • πŸ“§ Email: tsss1552@gmail.com (Repository Owner)
  • πŸ§‘β€πŸ’» Or directly message a maintainer via GitHub profile contact.

Please include:

  • A clear description of the issue
  • Steps to reproduce the vulnerability (if applicable)
  • Possible impact and suggested fix (if known)

πŸ•’ Response Time

We aim to respond to all security reports within 48 hours and provide a resolution or mitigation plan as soon as possible.


βœ… Best Practices for Contributors

To keep this project secure:

  • Avoid pushing any API keys, tokens, or sensitive data to the repository.
  • Always use environment variables for secrets.
  • Before raising a PR, run local security checks (e.g., npm audit fix).
  • Use updated dependencies β€” avoid known-vulnerable package versions.

πŸ’¬ Questions?

If you’re unsure about a security-related topic, feel free to ask in the Discussions tab or reach out to maintainers directly.


Thank you for helping keep en-git safe and secure! πŸ’™

There aren’t any published security advisories