@slango.configs/vitest
Slango vitest configs
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped config package for vitest; not a typosquat of vite. Name is intentional and consistent across 73 versions. | ai | |
| phantom-deps | phantom-dep:jsdom | AI (phantom-deps): Config package re-exports testing environment deps by convention; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@swc/core | AI (phantom-deps): Config package; @swc/core loaded via unplugin-swc by convention. | ai | |
| phantom-deps | phantom-dep:@testing-library/dom | AI (phantom-deps): Framework-scoped testing dep loaded by convention in vitest config. | ai | |
| phantom-deps | phantom-dep:@testing-library/react | AI (phantom-deps): Framework-scoped testing dep loaded by convention in vitest config. | ai | |
| phantom-deps | phantom-dep:@testing-library/jest-dom | AI (phantom-deps): Framework-scoped testing dep loaded by convention in vitest config. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 2.0.33 | 7 / 3 | |
| 2.0.32 | 7 / 3 | |
| 2.0.31 | 7 / 3 | |
| 2.0.30 | 7 / 3 | |
| 2.0.29 | 7 / 3 | |
| 2.0.28 | 7 / 3 | |
| 2.0.27 | 7 / 3 | |
| 2.0.26 | 7 / 3 | |
| 2.0.25 | 7 / 3 | |
| 2.0.24 | 7 / 3 | |
| 2.0.23 | 7 / 3 | |
| 2.0.22 | 7 / 3 | |
| 2.0.21 | 7 / 3 | |
| 2.0.20 | 7 / 3 | |
| 2.0.19 | 7 / 3 | |
| 2.0.18 | 7 / 3 | |
| 2.0.17 | 7 / 3 | |
| 2.0.16 | 7 / 3 | |
| 2.0.15 | 7 / 3 | |
| 2.0.14 | 7 / 3 | |
| 2.0.13 | 7 / 3 | |
| 2.0.11 | 7 / 3 | |
| 2.0.10 | 7 / 3 | |
| 2.0.9 | 7 / 3 | |
| 2.0.8 | 7 / 3 | |
| 2.0.7 | 7 / 3 | |
| 2.0.6 | 7 / 3 | |
| 2.0.5 | 7 / 3 | |
| 2.0.4 | 7 / 3 | |
| 2.0.3 | 7 / 3 | |
| 2.0.2 | 7 / 3 | |
| 2.0.1 | 7 / 3 | |
| 2.0.0 | 7 / 3 | |
| 1.0.49 | 8 / 7 | |
| 1.0.48 | 8 / 6 | |
| 1.0.47 | 8 / 6 | |
| 1.0.46 | 8 / 6 | |
| 1.0.45 | 8 / 6 | |
| 1.0.44 | 8 / 6 | |
| 1.0.43 | 8 / 6 | |
| 1.0.42 | 8 / 6 | |
| 1.0.41 | 8 / 6 | |
| 1.0.40 | 8 / 6 | |
| 1.0.39 | 8 / 6 |
v2.0.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.