Dependency audit fails at high: bump vulnerable dependencies

Abierto
  • ¿Algo no está bien?
#463 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
node.js, typescript, vite
Área
devops, security

Línea de trabajo

Start with pnpm why <module> for each listed vulnerable dependency and inspect the dependency declarations and lockfile. Bump dependencies or add pnpm.overrides where no patched version exists, following the tinypool override example in the shared actions repository. Run pnpm audit --audit-level high; done means the audit job passes.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug dependencies
Which package is this bug report for?

other

Issue description

pnpm audit --audit-level high fails on main: 37 advisories (4 low, 17 moderate, 14 high, 2 critical). All of them are in third-party dependencies and already public in the GitHub advisory database.

High and critical (module, vulnerable range → patched):

  • critical tinypool <2.1.2 → >=2.1.2
  • high vite >=8.2.0 <=8.2.3 → >=8.2.4
  • high zod <4.6.6 → >=4.6.6
  • high brace-expansion 2.x / 4.x–5.x → >=2.1.6 / >=5.0.11
  • high fast-uri <3.1.7 → >=3.1.7
  • high source-map-js <1.2.2 → >=1.2.2
  • high lodash.set >=3.7.0 <=4.3.2 → no patched version (needs the dependent replaced or overridden)

After the move to the shared nanoforge-dev/actions@v3 tests workflow (branch ci/actions-v3), the new Tests / Dependency audit job runs this check at high on every PR, so it stays red until these are bumped (pnpm why <module>, then dependency bumps or pnpm.overrides, as the actions repo did with tinypool: ^2.1.2).

Found while migrating engine CI to actions v3.

Code sample

No response

Versions
  • Engine main at 31ed3b8
  • pnpm 12.0.0, Node.js 26
Issue priority

Medium (should be fixed soon)

I have tested this issue on a development release

31ed3b8

Lenguaje dominante
TypeScript
Estrellas
7
Forks
2
Merge medio
1 d 17 h
PR fusionados (30 d)
17

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de NanoForge-dev/Engine

Todos los issues de NanoForge-dev/Engine

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.