Firestore 9.4.0: request supported fix for transitive glob/minimatch security advisories

オープン
#9,805 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
12/100
issue の種類
リファクタリング
明瞭さ
説明が足りない
活発さ
活発
技術スタック
nodejs, typescript
領域
backend, security

調査の方向性

Start by reproducing the dependency chain with npm ls glob minimatch rimraf --all and npm audit --omit=dev in an empty project that installs [email protected] and @google-cloud/[email protected]. The work is a maintainer-level decision about the google-gax, gaxios and Firestore API version ranges, not a code change a newcomer can make alone. Done means a supported version combination that clears both advisories, confirmed by the maintainers.

索引モデルが issue の本文から書いたものです。

説明

Summary

@google-cloud/[email protected], installed through [email protected], resolves older Google Cloud dependencies that retain rimraf@5 → glob@10 → minimatch@9.

This causes production dependency audit findings for:

We are requesting a maintainer-supported dependency update rather than forcing incompatible major-version overrides.

Environment

Observed dependency chain

[email protected]
└── @google-cloud/[email protected]
    └── @google-cloud/[email protected]
        └── [email protected]
            └── [email protected]
                └── [email protected]
                    └── [email protected]

A separate nested gaxios dependency also retains rimraf 5.

This is a condensed dependency relationship from a locked runtime graph, not a runtime execution trace.

Why an ordinary update does not resolve the findings

The declared package ranges include:

  • Firestore 9.4.0 → Firestore API ^0.2.0
  • Firestore API 0.2.0 → google-gax ^5.0.0
  • rimraf 5 → glob ^10.3.7
  • glob 10.5.0 → minimatch ^9.0.4

The published security fixes begin at glob 14.0.2 and minimatch 11.0.1, outside those ranges.

Suggested reproduction

Using an empty directory:

npm init -y
npm install --save-exact --ignore-scripts [email protected] @google-cloud/[email protected]
npm ls @google-cloud/firestore @google-cloud/firestore-api google-gax gaxios rimraf glob minimatch --all
npm audit --omit=dev

These are suggested reproduction commands using public packages. Registry resolutions may change.

Compatibility experiments

We separately tested:

  1. Overriding Firestore API 0.2.0 with 0.7.1.
  2. Retaining Firestore API 0.2.0 while overriding google-gax 5.x with 6.14.0.

Both experiments produced zero findings in the isolated Node 22 runtime audit and passed 72 distinct regression tests (84 executions).

However, both changes cross the upstream packages' declared dependency ranges. Emulator success does not establish full API compatibility or real Google Cloud production compatibility.

Neither configuration was adopted for release.

Related upstream issues

  • #8969 — google-gax includes an apparently build-only rimraf dependency.
  • #8975 — rimraf appears unused as a production dependency in gax and gaxios.
  • #8868 — gcp-metadata retains an older gaxios version containing rimraf.

These reports concern earlier dependency problems but appear relevant to the current advisories.

Requested maintainer guidance

  1. Can a supported Firestore 9.x release update its generated Firestore API dependency to a compatible version using a safe google-gax/gaxios dependency tree?
  2. Could the older Google Cloud dependencies receive supported patches removing unused rimraf production dependencies?
  3. Can affected gcp-metadata dependencies move away from exact older gaxios pins where compatible?
  4. Is there an officially supported Firestore / Firestore API / google-gax version combination that clears these findings on Node 22?
  5. Which versions and migration steps should downstream users adopt?

We would appreciate guidance on the smallest supported dependency update that resolves these advisories without unsupported major-version overrides.

主要言語
TypeScript
スター
3.2k
フォーク
732
平均マージ
2日 11時間
マージ済み PR(30日)
99

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

googleapis/google-cloud-node のほかの issue

googleapis/google-cloud-node の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。