@sk-web-gui/react
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@sk-web-gui/alert | AI (dependencies): Same-namespace sibling package; consistent with this package's pattern of aggregating @sk-web-gui/* components. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/avatar | AI (dependencies): First-party @sk-web-gui sub-package; same org as parent. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/pagination | AI (dependencies): First-party @sk-web-gui sub-package; same org as parent. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/searchfield | AI (dependencies): First-party @sk-web-gui sub-package; same org as parent. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/progress-stepper | AI (dependencies): First-party @sk-web-gui sub-package; same org as parent. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/forms | AI (dependencies): First-party @sk-web-gui sub-package; same org as parent. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/image | AI (dependencies): First-party @sk-web-gui sub-package; same org as parent. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/spinner | AI (dependencies): First-party @sk-web-gui sub-package; same org as parent. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; missing description is a known pattern for this org. | ai | |
| phantom-deps | phantom-dep:@sk-web-gui/text-editor | AI (phantom-deps): Same-org scoped package; phantom-dep pattern consistent with monorepo re-export bundle. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Missing metadata is typical for monorepo sub-packages; not indicative of spam/malware. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.0.15 | 37 / 2 | |
| 3.0.14 | 37 / 2 | |
| 3.0.12 | 37 / 2 | |
| 3.0.11 | 37 / 2 | |
| 3.0.9 | 36 / 2 | |
| 3.0.8 | 36 / 2 | |
| 3.0.7 | 36 / 2 | |
| 3.0.6 | 36 / 2 | |
| 3.0.5 | 36 / 2 | |
| 3.0.4 | 36 / 2 | |
| 3.0.3 | 36 / 2 | |
| 3.0.0 | 37 / 2 |
v3.0.15
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 (jerkerosatiesk) 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.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
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 (jerkerosatiesk) on 2026-04-16, 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.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.