@sk-web-gui/cookie-consent
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/forms | AI (dependencies): Same @sk-web-gui monorepo family; consistent pattern across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all versions and not a risk indicator here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo component; missing metadata is a pattern across the @sk-web-gui namespace, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with @sk-web-gui monorepo package style; not a malice signal. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.1.18 | 5 / 1 | |
| 2.1.17 | 5 / 1 | |
| 2.1.16 | 5 / 1 | |
| 2.1.15 | 5 / 1 | |
| 2.1.14 | 5 / 1 | |
| 2.1.12 | 5 / 1 | |
| 2.1.10 | 5 / 1 | |
| 2.1.9 | 5 / 1 | |
| 2.1.8 | 5 / 1 | |
| 2.1.7 | 5 / 1 | |
| 2.1.6 | 5 / 1 |
v2.1.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 (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.1.17
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.
v2.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.