Create SECURITY.md for security policy

[Frapucinoo]

Added a security policy document outlining supported versions and vulnerability reporting.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Summary of Changes

Hello @Frapucinoo, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a crucial SECURITY.md file to the project. This document serves as a central resource for users and contributors, clearly defining the project's security posture by listing supported versions for security updates and providing a structured process for reporting any discovered vulnerabilities. Its addition aims to enhance the project's security transparency and incident response capabilities.

Highlights

• New Security Policy Document: A new file, SECURITY.md, has been added to the repository to establish a formal security policy.
• Supported Versions: The SECURITY.md document includes a section detailing which versions of the project are currently supported with security updates, using a clear table format.
• Vulnerability Reporting Guidelines: The new policy outlines instructions on how to report security vulnerabilities, guiding users through the process and what to expect.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a SECURITY.md file, which is a great step for the project's security posture. However, the current file consists mainly of placeholder text from the GitHub template. My review includes critical feedback to replace this placeholder content with specific, actionable information. Key areas to address are defining the actual supported versions and, most importantly, providing a clear and private process for reporting vulnerabilities. Completing these sections is essential for the security policy to be effective.

[gemini-code-assist]

This section contains placeholder text and lacks the essential information for reporting a vulnerability. It's critical to provide a clear, private channel for security researchers to report issues. You should replace this with concrete instructions, including where to report, expected response times, and the process for handling confirmed vulnerabilities. Using GitHub's private vulnerability reporting feature is a recommended practice.

Suggested change

	Use this section to tell people how to report a vulnerability.
	Tell them where to go, how often they can expect to get an update on a
	reported vulnerability, what to expect if the vulnerability is accepted or
	declined, etc.
	We take all security vulnerabilities seriously. To report a security issue, please use the **[Private Vulnerability Reporting](https://github.com/google/androidify/security/advisories/new)** feature on GitHub.
	### Our Commitment
	We will make every effort to acknowledge your report within 48 hours. You can expect a more detailed response within 72 hours, indicating the next steps in handling your report. We appreciate your efforts to disclose your findings responsibly and will credit you for your discovery unless you prefer to remain anonymous.

[gemini-code-assist]

The versions listed in the support table appear to be examples and do not seem to align with the project's current state as described in the README.md. Please update this table to reflect the actual versions of the project and their support status. If no official versions have been released yet, it would be clearer to state that or prepare the table for upcoming releases (e.g., 1.0.x).