@sk-web-gui/list
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:jest | AI (typosquat): Scoped @sk-web-gui package; 2-edit distance to 'jest' is coincidental, not a typosquat attempt. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.2.9 | 2 / 1 | |
| 1.2.8 | 2 / 1 | |
| 1.2.7 | 2 / 1 | |
| 1.2.6 | 2 / 1 | |
| 1.2.5 | 2 / 1 |
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.