@yahoo/uds
Yahoo Universal System
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @yahoo/uds is Yahoo's design system; Levenshtein match to 'qs' is a false positive. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a legitimate runtime dep in package.json for a design system; phantom detection is a false positive. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): semver is a legitimate runtime dep in package.json; phantom detection is a false positive. | ai |
Versions (showing 19 of 119)
| Version | Deps | Published |
|---|---|---|
| 3.110.0 | 14 / 32 | |
| 3.109.0 | 14 / 32 | |
| 3.108.2 | 14 / 32 | |
| 3.108.1 | 14 / 32 | |
| 3.108.0 | 14 / 32 | |
| 3.107.1 | 14 / 32 | |
| 3.107.0 | 14 / 32 | |
| 3.106.0 | 14 / 32 | |
| 3.105.1 | 14 / 32 | |
| 3.105.0 | 14 / 32 | |
| 3.104.0 | 14 / 32 | |
| 3.103.0 | 14 / 32 | |
| 3.102.0 | 14 / 32 | |
| 3.101.0 | 14 / 32 | |
| 3.100.0 | 14 / 32 | |
| 3.99.0 | 14 / 31 | |
| 3.98.0 | 14 / 31 | |
| 3.97.0 | 14 / 31 | |
| 3.96.0 | 14 / 31 |
v3.110.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.109.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.108.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.108.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.108.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.107.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.107.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.106.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.105.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.105.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.104.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.103.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.102.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.101.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.100.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.99.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.98.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.97.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.96.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.