@vitest/eslint-plugin
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:https://veritemugabo.com/ | AI (email-domain): Author field contains a URL, not an email; domain check is a false positive for this package. | ai |
Versions (showing 59 of 59)
| Version | Deps | Published |
|---|---|---|
| 1.6.18 | 2 / 21 | |
| 1.6.17 | 2 / 21 | |
| 1.6.16 | 2 / 21 | |
| 1.6.15 | 2 / 21 | |
| 1.6.14 | 2 / 21 | |
| 1.6.13 | 2 / 21 | |
| 1.6.12 | 2 / 21 | |
| 1.6.11 | 2 / 21 | |
| 1.6.10 | 2 / 21 | |
| 1.6.9 | 2 / 21 | |
| 1.6.8 | 2 / 21 | |
| 1.6.7 | 2 / 21 | |
| 1.6.6 | 2 / 21 | |
| 1.6.5 | 2 / 21 | |
| 1.6.4 | 2 / 21 | |
| 1.6.3 | 2 / 21 | |
| 1.6.1 | 2 / 21 | |
| 1.5.4 | 2 / 21 | |
| 1.5.2 | 2 / 21 | |
| 1.5.1 | 2 / 21 | |
| 1.5.0 | 2 / 21 | |
| 1.4.4 | 2 / 21 | |
| 1.4.3 | 2 / 21 | |
| 1.4.2 | 2 / 21 | |
| 1.4.1 | 2 / 21 | |
| 1.4.0 | 2 / 21 | |
| 1.3.26 | 2 / 21 | |
| 1.3.25 | 2 / 21 | |
| 1.3.24 | 2 / 21 | |
| 1.3.23 | 2 / 18 | |
| 1.3.22 | 2 / 18 | |
| 1.3.20 | 2 / 18 | |
| 1.3.19 | 2 / 20 | |
| 1.3.18 | 2 / 20 | |
| 1.3.17 | 2 / 20 | |
| 1.3.16 | 2 / 20 | |
| 1.3.15 | 2 / 20 | |
| 1.3.14 | 2 / 20 | |
| 1.3.13 | 2 / 20 | |
| 1.3.12 | 2 / 20 | |
| 1.3.10 | 2 / 20 | |
| 1.3.9 | 2 / 20 | |
| 1.3.8 | 2 / 20 | |
| 1.3.7 | 2 / 20 | |
| 1.3.6 | 2 / 20 | |
| 1.3.5 | 2 / 20 | |
| 1.3.4 | 1 / 21 | |
| 1.3.3 | 1 / 21 | |
| 1.3.2 | 1 / 21 | |
| 1.3.1 | 1 / 21 | |
| 1.3.0 | 1 / 21 | |
| 1.2.7 | 1 / 21 | |
| 1.2.5 | 1 / 19 | |
| 1.2.4 | 1 / 19 | |
| 1.2.3 | 1 / 19 | |
| 1.2.2 | 1 / 19 | |
| 1.2.1 | 1 / 19 | |
| 1.2.0 | 1 / 19 | |
| 1.1.44 | 0 / 20 |
v1.6.18
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.17
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.16
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.15
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.14
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.13
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.12
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.11
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.10
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.9
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.8
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.7
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.26
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.25
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.24
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.23
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.22
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.20
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.19
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.18
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.17
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.16
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.15
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.14
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.13
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.12
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.10
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.44
2 findingsMaintainer email 'https://veritemugabo.com/' uses domain 'https://veritemugabo.com/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.