Skip to content

Security: Abhishek2634/Foodie

Security

SECURITY.md

πŸ” Security Policy

Supported Versions

We actively maintain the latest version of the Foodie project. Please ensure you're always using the most recent release to benefit from the latest features and security updates.

Version Supported
latest βœ…
older ❌

πŸ“’ Reporting a Vulnerability

If you discover a security vulnerability in this project, do not open an issue directly on GitHub.

Instead, please follow these steps:

  1. Contact us directly via email.

  2. Provide a clear and detailed description of the issue, including:

    • Steps to reproduce the vulnerability
    • The impact it could have
    • Any recommended fixes (if available)
  3. Allow us a reasonable time to investigate and fix the vulnerability before disclosing it publicly.


πŸ” Security Best Practices

To help keep the Foodie app and its users secure, please follow these best practices:

  • Never share sensitive credentials or API keys in public repositories.
  • Use environment variables to store secrets and tokens.
  • Always run the latest version of dependencies.
  • Perform regular audits using tools like npm audit or yarn audit.

πŸ›‘οΈ Scope of Security

This security policy applies to:

  • The source code in this repository
  • Configuration files
  • Dependencies defined in package.json

Note: Issues related to third-party services or APIs used by the app (e.g., payment gateways, external APIs) should be reported to those service providers.


🀝 Responsible Disclosure

We appreciate responsible disclosure of any vulnerability. All security reports will be acknowledged and investigated promptly. We are committed to maintaining a secure and safe environment for all contributors and users.

Thank you for helping keep Foodie secure! 🍽️

There aren’t any published security advisories