Skip to content

Add license field into package.json#14473

Merged
scidomino merged 4 commits intogoogle-gemini:mainfrom
jb-perez:patch-1
Dec 12, 2025
Merged

Add license field into package.json#14473
scidomino merged 4 commits intogoogle-gemini:mainfrom
jb-perez:patch-1

Conversation

@jb-perez
Copy link
Copy Markdown
Contributor

@jb-perez jb-perez commented Dec 3, 2025

Add the license field in the package.json to reflect the project license.

Summary

Add the license information into the package.json to reflect the project license.

Details

License field is used by different systems to quickly identify the project license.

How to Validate

Verify license property is present.

Pre-Merge Checklist

  • Updated relevant documentation and README (if needed)
  • Added/updated tests (if needed)
  • Noted breaking changes (if any)
  • Validated on required platforms/methods:
    • MacOS
      • npm run
      • npx
      • Docker
      • Podman
      • Seatbelt
    • Windows
      • npm run
      • npx
      • Docker
    • Linux
      • npm run
      • npx
      • Docker

Add the license field in the package.json to reflect the project license.
@jb-perez jb-perez requested a review from a team as a code owner December 3, 2025 22:45
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @jb-perez, 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 updates the project's package.json to explicitly include the license information. This change ensures that the project's licensing terms are clearly stated within its metadata, which is beneficial for various systems and tools that rely on this field for compliance and project identification.

Highlights

  • License Field Addition: The license field has been added to the package.json file.
  • License Type: The specified license for the project is "Apache-2.0".
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.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request correctly adds the license field to the root package.json. However, it overlooks adding the same field to the public, publishable packages within the monorepo's packages directory. I've added a comment with details on which packages need to be updated to fully address license declaration for the project.

Comment thread package.json Outdated
{
"name": "@google/gemini-cli",
"version": "0.21.0-nightly.20251202.2d935b379",
"license": "Apache-2.0",
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.

high

Adding the license to the root package.json is a good first step. However, this package is marked as private (via "private": "true") and is not published. The public packages that are distributed to users are still missing their license information. To properly declare the project's license, please add "license": "Apache-2.0" to the package.json of each public package in the packages/ directory, specifically for @google/gemini-cli, @google/gemini-cli-core, and @google/gemini-cli-a2a-server.

@scidomino scidomino enabled auto-merge December 12, 2025 20:19
@scidomino scidomino added this pull request to the merge queue Dec 12, 2025
Merged via the queue into google-gemini:main with commit d2a1a45 Dec 12, 2025
22 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.

2 participants