@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 100 of 119)
| Version | Deps | Published |
|---|---|---|
| 3.163.2 | 19 / 33 | |
| 3.163.1 | 19 / 33 | |
| 3.163.0 | 19 / 33 | |
| 3.162.2 | 19 / 33 | |
| 3.162.1 | 19 / 33 | |
| 3.162.0 | 19 / 33 | |
| 3.161.0 | 19 / 33 | |
| 3.160.0 | 19 / 33 | |
| 3.159.2 | 19 / 33 | |
| 3.159.1 | 19 / 33 | |
| 3.159.0 | 19 / 33 | |
| 3.158.1 | 19 / 33 | |
| 3.158.0 | 19 / 33 | |
| 3.157.1 | 19 / 33 | |
| 3.157.0 | 19 / 33 | |
| 3.156.2 | 19 / 33 | |
| 3.156.1 | 19 / 33 | |
| 3.156.0 | 19 / 33 | |
| 3.155.0 | 19 / 33 | |
| 3.154.1 | 19 / 33 | |
| 3.154.0 | 19 / 33 | |
| 3.153.2 | 19 / 33 | |
| 3.153.1 | 19 / 33 | |
| 3.153.0 | 18 / 33 | |
| 3.152.1 | 18 / 33 | |
| 3.152.0 | 18 / 33 | |
| 3.151.0 | 18 / 33 | |
| 3.150.0 | 18 / 33 | |
| 3.149.0 | 18 / 33 | |
| 3.148.0 | 18 / 33 | |
| 3.147.0 | 18 / 33 | |
| 3.146.0 | 18 / 33 | |
| 3.145.0 | 18 / 33 | |
| 3.144.2 | 17 / 29 | |
| 3.144.1 | 17 / 29 | |
| 3.144.0 | 17 / 29 | |
| 3.143.0 | 17 / 29 | |
| 3.142.0 | 17 / 29 | |
| 3.141.0 | 17 / 29 | |
| 3.140.0 | 18 / 29 | |
| 3.139.0 | 18 / 29 | |
| 3.138.0 | 18 / 29 | |
| 3.137.2 | 18 / 29 | |
| 3.137.1 | 18 / 29 | |
| 3.137.0 | 18 / 29 | |
| 3.136.0 | 18 / 29 | |
| 3.135.0 | 18 / 29 | |
| 3.134.2 | 18 / 29 | |
| 3.134.1 | 18 / 29 | |
| 3.134.0 | 18 / 29 | |
| 3.133.3 | 18 / 29 | |
| 3.133.2 | 18 / 29 | |
| 3.133.1 | 18 / 29 | |
| 3.133.0 | 18 / 29 | |
| 3.132.2 | 18 / 29 | |
| 3.132.1 | 18 / 29 | |
| 3.132.0 | 18 / 29 | |
| 3.131.0 | 18 / 29 | |
| 3.130.1 | 18 / 29 | |
| 3.130.0 | 18 / 29 | |
| 3.129.0 | 18 / 29 | |
| 3.128.1 | 18 / 29 | |
| 3.128.0 | 18 / 29 | |
| 3.127.1 | 18 / 29 | |
| 3.127.0 | 18 / 29 | |
| 3.126.0 | 18 / 29 | |
| 3.125.1 | 18 / 29 | |
| 3.125.0 | 18 / 29 | |
| 3.124.0 | 18 / 29 | |
| 3.123.0 | 18 / 29 | |
| 3.122.3 | 18 / 29 | |
| 3.122.2 | 18 / 29 | |
| 3.122.1 | 18 / 29 | |
| 3.122.0 | 18 / 29 | |
| 3.121.0 | 18 / 29 | |
| 3.120.0 | 18 / 29 | |
| 3.119.2 | 18 / 29 | |
| 3.119.1 | 18 / 29 | |
| 3.119.0 | 18 / 29 | |
| 3.118.0 | 18 / 29 | |
| 3.117.6 | 18 / 29 | |
| 3.117.5 | 18 / 29 | |
| 3.117.4 | 18 / 29 | |
| 3.117.3 | 18 / 29 | |
| 3.117.2 | 18 / 29 | |
| 3.117.1 | 18 / 29 | |
| 3.117.0 | 18 / 29 | |
| 3.116.3 | 18 / 29 | |
| 3.116.2 | 18 / 29 | |
| 3.116.1 | 18 / 29 | |
| 3.116.0 | 18 / 29 | |
| 3.115.3 | 18 / 29 | |
| 3.115.2 | 18 / 29 | |
| 3.115.1 | 18 / 29 | |
| 3.115.0 | 18 / 29 | |
| 3.114.0 | 14 / 32 | |
| 3.113.0 | 14 / 32 | |
| 3.112.1 | 14 / 32 | |
| 3.112.0 | 14 / 32 | |
| 3.111.0 | 14 / 32 |
v3.163.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.163.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.163.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.162.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.162.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.162.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.161.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.160.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.159.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.159.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.159.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.158.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.158.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.122.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.122.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.122.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.122.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.121.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.120.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.119.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.119.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.119.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.118.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.117.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.117.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.117.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.117.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.117.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.117.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.117.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.116.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.116.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.116.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.116.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.115.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.115.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.115.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.115.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.114.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.113.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.112.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.112.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.111.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.