add a security vulnerability description

[alcholiclg]

Change Summary

1. add a security vulnerability description

Related issue number

Checklist

• The pull request title is a good summary of the changes - it will be used in the changelog
• Unit tests for the changes exist
• Run pre-commit install and pre-commit run --all-files before git commit, and passed lint check.
• Documentation reflects the changes where applicable

[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 formal security policy for the MS-Agent project by adding a SECURITY.md file. This document provides clear instructions for users and researchers on how to responsibly report security vulnerabilities, details the types of issues considered in-scope, and describes the project's disclosure process to ensure timely and coordinated resolution of security concerns.

Highlights

• Security Policy: A new SECURITY.md file has been added to establish a clear process for reporting security vulnerabilities, outlining reporting guidelines, scope, and disclosure procedures.

🧠 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

• .github/SECURITY.md
  • Added a new security policy document.

Activity

• No specific activity (comments, reviews, progress updates) was found in the provided context.

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, establishing a formal security policy for the project. The document is clear and covers the essential procedures for reporting vulnerabilities, the scope of the policy, and the disclosure process. My review includes a suggestion to add a dedicated security email address as an alternative reporting channel, aligning with best practices and the policy of the parent ModelScope organization.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[gemini-code-assist]

It's good practice to provide a dedicated security email address as a fallback for reporting vulnerabilities. This is useful if GitHub's Private Vulnerability Reporting isn't enabled or if a reporter prefers email. The main ModelScope project uses security@modelscope.org. It would be beneficial to add this as an alternative contact method here as well.

Suggested change

	- **Preferred**: Use GitHub **Private Vulnerability Reporting** (Security → Advisories → Report a vulnerability), if enabled.
	- **Preferred**: Use GitHub **Private Vulnerability Reporting** (Security → Advisories → Report a vulnerability), if enabled.
	- **Alternative**: Email us at `security@modelscope.org`.