@warp-ds/css
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @warp-ds/css; Levenshtein match to 'cors' is a false positive based on suffix similarity only. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @warp-ds/css; Levenshtein match to 'qs' is a false positive based on suffix similarity only. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.4.1 | 0 / 21 | |
| 2.4.0 | 0 / 21 | |
| 2.3.0 | 0 / 21 | |
| 2.2.3 | 0 / 19 | |
| 2.2.2 | 0 / 19 | |
| 2.2.1 | 0 / 19 | |
| 2.1.1 | 0 / 19 |
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.