@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, so a manually published version cannot be tied back to a reviewed commit.
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 |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.40.0 | 12 / 0 | |
| 2.39.0 | 12 / 0 | |
| 2.38.0 | 12 / 0 | |
| 2.37.0 | 12 / 0 | |
| 2.36.0 | 12 / 0 | |
| 2.35.0 | 12 / 0 | |
| 2.34.0 | 12 / 0 | |
| 2.33.0 | 12 / 0 | |
| 2.32.0 | 12 / 0 |
v2.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.