@sk-web-gui/ai
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:hapi | AI (typosquat): Scoped package @sk-web-gui/ai cannot plausibly typosquat unscoped short names; Levenshtein on full scoped name is meaningless here. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same reasoning — scoped package vs. 2-char unscoped name is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Same reasoning — scoped package vs. 2-char unscoped name is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same reasoning — scoped package vs. short unscoped name is a false positive. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Same reasoning — scoped package vs. short unscoped name is a false positive. | ai | |
| phantom-deps | phantom-dep:@sk-web-gui/theme | AI (phantom-deps): Same-org scoped dep; likely re-exported or used via CSS/theme convention rather than direct import. | ai | |
| phantom-deps | phantom-dep:@types/sanitize-html | AI (phantom-deps): Type-only package; not imported at runtime, stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.4.3 | 24 / 1 | |
| 4.4.2 | 24 / 1 | |
| 4.4.0 | 24 / 1 | |
| 4.3.2 | 23 / 1 | |
| 3.1.0 | 22 / 1 | |
| 3.0.3 | 22 / 1 |
v4.4.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 (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.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
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.