To get started, use the following command as your [Ignored Build Step](https://vercel.com/docs/concepts/projects/overview#ignored-build-step):
82%
Total Score
healthy
Frequent releases and active Vercel backing support this package; concentrated commits and workflow audit findings add moderate risk.
Publishing is primarily tied to vercel.com accounts, consistent with the organization-backed repository; jaredpalmer (palmer.net) is an outside-domain publishing account and adds a minor account-hygiene concern.
One contributor made about 85% of recent commits, creating concentration risk, although 26 active contributors and organization backing provide meaningful compensation.
The repository name does not match turbo-ignore and its README does not mention the package, creating some uncertainty about package-to-repository ownership; the package appears to be a subpackage of the linked monorepo, which partly explains the mismatch.
All 12 workflows were analyzed with no untrusted checkout or script-injection findings and all 72 action references pinned; high-confidence template injection, inherited secrets, ad hoc package installs, and one broad write permission remain workflow-hygiene concerns.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2025-10894 Pre-CVE Found by Aikido Intel before public disclosure or CVE publication. turbo-ignore is vulnerable to Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in versions 1.10.14 - 2.6.2. | 1.10.14 - 2.6.2 | High |
| Dependency | Last Release | Score |
|---|---|---|
json5 Version 2.2.3 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.