turbo
Turborepo is a high-performance build system for JavaScript and TypeScript codebases.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:turbo-linux-mips64le | AI (phantom-deps): Platform-specific optional binary dependency — standard cross-platform binary distribution pattern for turbo. | ai | |
| phantom-deps | phantom-dep:turbo-linux-32 | AI (phantom-deps): Platform-specific optional binary dependency — standard cross-platform binary distribution pattern for turbo. | ai | |
| phantom-deps | phantom-dep:turbo-linux-arm | AI (phantom-deps): Platform-specific optional binary dependency — standard cross-platform binary distribution pattern for turbo. | ai | |
| phantom-deps | phantom-dep:turbo-freebsd-64 | AI (phantom-deps): Platform-specific optional binary dependency — standard cross-platform binary distribution pattern for turbo. | ai | |
| phantom-deps | phantom-dep:turbo-windows-32 | AI (phantom-deps): Platform-specific optional binary dependency — standard cross-platform binary distribution pattern for turbo. | ai | |
| phantom-deps | phantom-dep:turbo-freebsd-arm64 | AI (phantom-deps): Platform-specific optional binary dependency — standard cross-platform binary distribution pattern for turbo. | ai | |
| phantom-deps | phantom-dep:turbo-linux-ppc64le | AI (phantom-deps): Platform-specific optional binary dependency — standard cross-platform binary distribution pattern for turbo. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): turbo's postinstall runs install.js to select and install the correct platform-specific binary — standard documented pattern for cross-platform binary distribution, stable across versions. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): process.env spread is used to sanitize npm_config_global to prevent install deadlock — defensive pattern, not credential exfiltration. Confirmed in public Vercel/turborepo source. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used to run nested npm install for platform binary selection — expected and documented behavior for turbo's binary installer. | ai | |
| phantom-deps | phantom-dep:turbo-darwin-64 | AI (phantom-deps): Platform-specific optional binary dependency; standard pattern for cross-platform CLI tools. | ai | |
| phantom-deps | phantom-dep:turbo-windows-64 | AI (phantom-deps): Platform-specific optional binary dependency; standard pattern for cross-platform CLI tools. | ai | |
| phantom-deps | phantom-dep:turbo-linux-arm64 | AI (phantom-deps): Platform-specific optional binary dependency; standard pattern for cross-platform CLI tools. | ai | |
| phantom-deps | phantom-dep:turbo-darwin-arm64 | AI (phantom-deps): Platform-specific optional binary dependency; standard pattern for cross-platform CLI tools. | ai | |
| phantom-deps | phantom-dep:turbo-windows-arm64 | AI (phantom-deps): Platform-specific optional binary dependency; standard pattern for cross-platform CLI tools. | ai | |
| phantom-deps | phantom-dep:turbo-linux-64 | AI (phantom-deps): Platform-specific optional binary dependency; standard pattern for cross-platform CLI tools. | ai |
Versions (showing 51 of 199)
| Version | Deps | Published |
|---|---|---|
| 2.9.16 | 0 / 0 | |
| 2.9.15 | 0 / 0 | |
| 2.9.14 | 0 / 0 | |
| 2.9.12 | 0 / 0 | |
| 2.9.11 | 0 / 0 | |
| 2.9.10 | 0 / 0 | |
| 2.9.9 | 0 / 0 | |
| 2.9.8 | 0 / 0 | |
| 2.9.7 | 0 / 0 | |
| 2.9.6 | 0 / 0 | |
| 2.9.5 | 0 / 0 | |
| 2.9.4 | 0 / 0 | |
| 2.9.3 | 0 / 0 | |
| 2.9.2 | 0 / 0 | |
| 2.9.1 | 0 / 0 | |
| 2.9.0 | 0 / 0 | |
| 2.8.21 | 0 / 0 | |
| 2.8.20 | 0 / 0 | |
| 2.8.19 | 0 / 0 | |
| 2.8.18 | 0 / 0 | |
| 2.8.17 | 0 / 0 | |
| 2.8.16 | 0 / 0 | |
| 2.8.15 | 0 / 0 | |
| 2.8.14 | 0 / 0 | |
| 2.8.13 | 0 / 0 | |
| 2.8.12 | 0 / 0 | |
| 2.8.11 | 0 / 0 | |
| 2.8.10 | 0 / 0 | |
| 2.8.9 | 0 / 0 | |
| 2.8.8 | 0 / 0 | |
| 2.8.7 | 0 / 0 | |
| 2.8.6 | 0 / 0 | |
| 2.8.5 | 0 / 0 | |
| 2.8.4 | 0 / 0 | |
| 2.8.3 | 0 / 0 | |
| 2.8.2 | 0 / 0 | |
| 2.8.1 | 0 / 0 | |
| 2.8.0 | 0 / 0 | |
| 2.7.6 | 0 / 0 | |
| 2.7.5 | 0 / 0 | |
| 2.7.4 | 0 / 0 | |
| 2.7.3 | 0 / 0 | |
| 2.7.2 | 0 / 0 | |
| 2.7.1 | 0 / 0 | |
| 2.7.0 | 0 / 0 | |
| 2.6.3 | 0 / 0 | |
| 2.6.2 | 0 / 0 | |
| 2.6.1 | 0 / 0 | |
| 2.6.0 | 0 / 0 | |
| 2.5.8 | 0 / 0 | |
| 2.5.7 | 0 / 0 |
v2.9.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.