@sk-web-gui/text
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:next | AI (typosquat): Scoped @sk-web-gui component package; not a typosquat of next. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): Scoped @sk-web-gui component package; not a typosquat of nuxt. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @sk-web-gui component package; not a typosquat of jest. | ai |
v1.1.9
2 findingsPackage name '@sk-web-gui/text' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
2 findingsPackage name '@sk-web-gui/text' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.