@s-ui/js
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by org maintainer cleanup; publisher is a known maintainer with prior approvals on this package. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Same scoped-package context; not impersonating jest. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same scoped-package context; not impersonating pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @s-ui/js is a scoped package in the Schibsted UI monorepo; short-name Levenshtein match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same scoped-package context; not impersonating joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Same scoped-package context; not impersonating ajv. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): Same scoped-package context; not impersonating rxjs. | ai |
v2.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.39.0
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 (francisco.ruiz.lloret) than the most recent previously approved version (schibstedspain) on 2026-06-04, but francisco.ruiz.lloret 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.38.0
2 findingsPackage name '@s-ui/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.