@sk-web-gui/table
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance across this org's packages; consistent pattern, not a per-version risk. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped component library package; missing description is a stable pattern across this org's packages. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/forms | AI (dependencies): Same-org sibling package; consistent pattern across all @sk-web-gui/* components. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/utils | AI (dependencies): Same-org sibling package; consistent pattern across all @sk-web-gui/* components. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/pagination | AI (dependencies): Same-org sibling package; consistent pattern across all @sk-web-gui/* components. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/theme | AI (dependencies): Same-org sibling package; consistent pattern across all @sk-web-gui/* components. | ai | |
| dependencies | unvetted-dep:@sk-web-gui/icon | AI (dependencies): Same-org sibling package; consistent pattern across all @sk-web-gui/* components. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing metadata is structural, not indicative of spam/malware. | ai | |
| phantom-deps | phantom-dep:@sk-web-gui/theme | AI (phantom-deps): Same-org dep; phantom import in a monorepo build is a stable false positive. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.2.19 | 8 / 1 | |
| 3.2.18 | 8 / 1 | |
| 3.2.17 | 8 / 1 | |
| 3.2.16 | 8 / 1 | |
| 3.2.15 | 8 / 1 | |
| 3.2.14 | 8 / 1 | |
| 3.2.13 | 8 / 1 | |
| 3.2.11 | 8 / 1 | |
| 3.2.10 | 8 / 1 | |
| 3.2.9 | 8 / 1 | |
| 3.2.8 | 8 / 1 | |
| 3.2.7 | 8 / 1 | |
| 3.2.6 | 8 / 1 |
v3.2.19
2 findings[Accepted risk] Package 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.
v3.2.18
2 findings[Accepted risk] Package 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.
v3.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.