Create SECURITY.md for security policy

[Sarvardin]

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, 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 comprehensive security policy document, SECURITY.md, to the repository. Its purpose is to clearly communicate the project's stance on security, including which versions receive active security support and the established procedure for reporting potential vulnerabilities. This addition enhances transparency and provides a structured approach for handling security concerns, benefiting both contributors and users.

Highlights

• New Security Policy Document: A new SECURITY.md file has been added to the repository, providing clear guidelines for security-related matters.
• Supported Versions: The document outlines which versions of the project are currently supported with security updates, specifically marking 5.1.x and 4.0.x as supported, and 5.0.x and < 4.0 as unsupported.
• Vulnerability Reporting Guidelines: Instructions are included on how to report vulnerabilities, what to expect regarding updates, and the process for accepted or declined reports.

🧠 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.

Changelog

• SECURITY.md
  • Added a new file to define the project's security policy.
  • Included a section detailing supported and unsupported versions for security updates.
  • Provided guidelines for reporting vulnerabilities and the expected process.

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 an important step for defining the project's security process. However, the current file is a template with placeholder content. For this document to be effective, it needs to be populated with the project's specific policies for supported versions and vulnerability reporting. I've added a comment to highlight the need to fill in this information.

[gemini-code-assist]

This SECURITY.md file appears to be the default template provided by GitHub. While it's a good start, it currently contains only placeholder text and examples. To make it useful, it needs to be filled out with the project's specific security policy, including:

• Supported Versions: The actual versions of the project that receive security updates.
• Reporting a Vulnerability: A clear, concrete process for how to report vulnerabilities (e.g., via GitHub's private reporting feature or a specific email address), and what reporters can expect in terms of response.

An incomplete security policy can be misleading. Please update this file with the project's actual policies.