@sk-web-gui/filter
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): Consistent across all versions of this package; no provenance is the norm for this org's packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): 865-day-old package with 38 versions; sparse metadata is a style choice for this org's monorepo, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across this org's packages; not a malice signal. | ai | |
| phantom-deps | phantom-dep:@sk-web-gui/badge | AI (phantom-deps): Same-org sibling dep; phantom detection likely a false positive from re-exported types or indirect usage. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.2.18 | 3 / 1 | |
| 1.2.17 | 3 / 1 | |
| 1.2.16 | 3 / 1 | |
| 1.2.15 | 3 / 1 | |
| 1.2.9 | 3 / 1 | |
| 1.2.8 | 3 / 1 | |
| 1.2.7 | 3 / 1 | |
| 1.2.6 | 3 / 1 |
v1.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 (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.
v1.2.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.
v1.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.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.