Firestore 9.4.0: request supported fix for transitive glob/minimatch security advisories
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 12/100
- Tipo de issue
- Refactorización
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- nodejs, typescript
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 3.2k
- Forks
- 732
- Merge medio
- 2 d 11 h
- PR fusionados (30 d)
- 99
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de googleapis/google-cloud-node
-
Broken deprecation chainAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
googleapis/google-cloud-node#9854 ·
Los mantenedores suelen responder en 1 día
-
pubsub: "Operation attempted on ended Span" when a modack is flushed after the message was ackedAbiertoapi: pubsub
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
googleapis/google-cloud-node#9853 ·
Los mantenedores suelen responder en 1 día
-
storage: V4 getSignedUrl sorts canonical headers with localeCompare, so they disagree with X-Goog-SignedHeadersPosiblemente ocupada @itsrayeedscodespace la tomó hace 9 días. Abiertoapi: storage
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
googleapis/google-cloud-node#9840 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
firestore: getPartitions() emits gax AutopaginateTrueWarning in every processPosiblemente ocupada @TheRealDanii la tomó hace 12 días. Abiertoapi: firestore
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
googleapis/google-cloud-node#9736 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
googleapis/google-cloud-node#9723 ·
Los mantenedores suelen responder en 1 día
Todos los issues de googleapis/google-cloud-node
Issues similares
-
Type/Improvement
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
OpenNSW/nsw-srilanka#1259 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
oxc-project/tsrs#1010 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Fission-AI/OpenSpec#2260 ·
Los mantenedores suelen responder en 1 día
-
Add: ESP 1 UKAbiertocheck:passed streams:add
Dificultad 1/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día
-
area:infra area:storage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
THU-MAIC/OpenMAIC#2311 · 1 comentario ·
Los mantenedores suelen responder en 1 día