Firestore 9.4.0: request supported fix for transitive glob/minimatch security advisories
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 12/100
- issue の種類
- リファクタリング
- 明瞭さ
- 説明が足りない
- 活発さ
- 活発
- 技術スタック
- nodejs, typescript
調査の方向性
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:
- [GHSA-3g3m-2fjr-6pw4](https://github.com/advisories/GHSA-3g3m-2fjr-6pw4) — glob
- [GHSA-g3hv-75wg-m249](https://github.com/advisories/GHSA-g3hv-75wg-m249) — minimatch
We are requesting a maintainer-supported dependency update rather than forcing incompatible major-version overrides.
Environment
- Node.js 22
- npm 11
[email protected]@google-cloud/[email protected]@google-cloud/[email protected][email protected]- Nested
[email protected] [email protected][email protected][email protected]
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:
- Overriding Firestore API 0.2.0 with 0.7.1.
- 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
- 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?
- Could the older Google Cloud dependencies receive supported patches removing unused rimraf production dependencies?
- Can affected gcp-metadata dependencies move away from exact older gaxios pins where compatible?
- Is there an officially supported Firestore / Firestore API / google-gax version combination that clears these findings on Node 22?
- 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
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
googleapis/google-cloud-node のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
googleapis/google-cloud-node#9854 ·
メンテナーはふだん 1 日以内に返信
-
pubsub: "Operation attempted on ended Span" when a modack is flushed after the message was ackedオープンapi: pubsub
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
googleapis/google-cloud-node#9853 ·
メンテナーはふだん 1 日以内に返信
-
storage: V4 getSignedUrl sorts canonical headers with localeCompare, so they disagree with X-Goog-SignedHeaders対応中かも @itsrayeedscodespace が 9 日前に担当しました。 オープンapi: storage
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
googleapis/google-cloud-node#9840 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
firestore: getPartitions() emits gax AutopaginateTrueWarning in every process対応中かも @TheRealDanii が 12 日前に担当しました。 オープンapi: firestore
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
googleapis/google-cloud-node#9736 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 82/100
googleapis/google-cloud-node#9723 ·
メンテナーはふだん 1 日以内に返信
googleapis/google-cloud-node の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
oxc-project/tsrs#1010 ·
メンテナーはふだん 1 日以内に返信
-
area:infra area:storage bug
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
THU-MAIC/OpenMAIC#2311 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
docs documentation need-triage SaaS
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
enhancement from-app needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
nightly-labs/openbot#10973 ·
メンテナーはふだん 1 日以内に返信
-
status/need-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
google-gemini/gemini-cli#30328 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信