@sk-web-gui/forms
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 UI component package @sk-web-gui/forms; name similarity to cors is coincidental. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/icon | AI (dependencies): Same @sk-web-gui monorepo; sibling dep, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/link | AI (dependencies): Same @sk-web-gui monorepo; sibling dep. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/modal | AI (dependencies): Same @sk-web-gui monorepo; sibling dep. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/theme | AI (dependencies): Same @sk-web-gui monorepo; sibling dep. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/utils | AI (dependencies): Same @sk-web-gui monorepo; sibling dep. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/button | AI (dependencies): Same @sk-web-gui monorepo; sibling dep. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/divider | AI (dependencies): Same @sk-web-gui monorepo; sibling dep. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/popup-menu | AI (dependencies): Same @sk-web-gui monorepo; sibling dep. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.9.3 | 12 / 1 | |
| 2.9.2 | 12 / 1 | |
| 2.9.1 | 12 / 1 | |
| 2.9.0 | 12 / 1 | |
| 2.8.2 | 12 / 1 | |
| 2.8.1 | 12 / 1 | |
| 2.8.0 | 12 / 1 | |
| 2.7.1 | 12 / 1 | |
| 2.7.0 | 12 / 1 | |
| 2.6.1 | 12 / 1 | |
| 2.6.0 | 12 / 1 | |
| 2.5.0 | 12 / 1 | |
| 2.4.5 | 12 / 1 |
v2.9.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tobbe.nordin) than the most recent previously approved version (henrsand) on 2026-05-29, but tobbe.nordin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.9.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jerkerosatiesk) than the most recent previously approved version (henrsand) on 2026-05-06, but jerkerosatiesk is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.