turbo
2.11.13 · 18 Nov 2026MIT48.2M / weekRepositoryHomepagenpmAtom feed
Upgrading turbo From 2.8.3 to 2.8.4
1 release in betweenevery note read
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 18
- fixes
Security
2 advisories still affect 2.8.4
- Turbo: Unexpected local code execution during Yarn Berry detectionlow · GHSA-3qcw-2rhx-2726
- Turbo: Login callback CSRF/session fixationmoderate · GHSA-hcf7-66rw-9f5r
Upgrading to 2.9.14 clears them.
- 2.8.4
Upgrade semver to fix ReDoS vulnerability
- 2.8.4
Upgrade tsdown in create-turbo to resolve valibot ReDoS vulnerability
- 2.8.4
Upgrade jest to v30 to resolve brace-expansion ReDoS vulnerability
- 2.8.4
Upgrade Next.js to 16.1.5 to fix DoS vulnerabilities
- 2.8.4
Upgrade eslint to v10 to resolve @eslint/plugin-kit ReDoS vulnerability
- 2.8.4
Upgrade tar to 7.5.7 to address security vulnerabilities
- 2.8.4
Upgrade ts-json-schema-generator to fix glob command injection vulnerability
- 2.8.4
Upgrade fumadocs and shiki in docs to resolve mdast-util-to-hast vulnerability
- 2.8.4
Replace ts-node with tsx to resolve diff DoS vulnerability
Release by release
- Security
Upgrade semver to fix ReDoS vulnerability
- Security
Upgrade tsdown in create-turbo to resolve valibot ReDoS vulnerability
- Security
Upgrade jest to v30 to resolve brace-expansion ReDoS vulnerability
- Security
Upgrade Next.js to 16.1.5 to fix DoS vulnerabilities
- Security
8 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.