Skip to content

[DOCS] Clarify trusted usage#18718

Merged
tlopex merged 1 commit into
apache:mainfrom
tqchen:security
Feb 6, 2026
Merged

[DOCS] Clarify trusted usage#18718
tlopex merged 1 commit into
apache:mainfrom
tqchen:security

Conversation

@tqchen

@tqchen tqchen commented Feb 6, 2026

Copy link
Copy Markdown
Member

This docs clarifies trusted url requirements

This docs clarifies trusted url requirements
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @tqchen, I'm Gemini Code Assist1! 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 enhances the clarity of the TVM security documentation by explicitly stating that all TVM APIs are intended for use by trusted users. It further specifies that when APIs require URLs, only trusted URLs should be provided, reinforcing secure usage practices for the framework.

Highlights

  • Documentation Update: Added explicit clarification to the security documentation regarding the expectation that all TVM APIs are designed for trusted users.
  • Trusted URL Requirement: Emphasized that for TVM APIs involving URLs, users are expected to provide only trusted URLs.

🧠 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
  • docs/reference/security.rst
    • Added a new paragraph clarifying that all TVM APIs are designed for trusted users.
    • Included a statement emphasizing the requirement for trusted URLs when using APIs that involve URL parameters.
Activity
  • No human activity has been recorded on this pull request yet.
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 gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request clarifies the documentation regarding the expected trusted usage of TVM APIs, particularly for those involving URLs. This change enhances the clarity of security expectations for users.

Comment on lines +46 to +47
All of the TVM APIs are designed to be used by trusted users, for APIs that involves URL,
we expect users to put in only trusted URLs.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The phrasing in these lines can be improved for better grammatical correctness and flow. Specifically, "involves URL" should be "involve URLs" to match the plural "APIs". Additionally, splitting the thought into two distinct sentences can enhance readability.

Suggested change
All of the TVM APIs are designed to be used by trusted users, for APIs that involves URL,
we expect users to put in only trusted URLs.
All TVM APIs are designed for trusted users. For APIs that involve URLs, users are expected to provide only trusted URLs.

@tlopex tlopex merged commit 057aa10 into apache:main Feb 6, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants