@uniformdev/design-system
Uniform design system components
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:@react-icons/all-files | AI (npm-metadata): Points to a pinned tagged release tarball on the official react-icons repo; not a floating or untrusted URL. | ai | |
| phantom-deps | phantom-dep:@lexical/link | AI (phantom-deps): Lexical sub-packages are peer/transitive deps used via config; stable false positive for this design system. | ai | |
| phantom-deps | phantom-dep:monaco-editor | AI (phantom-deps): monaco-editor is loaded indirectly via @monaco-editor/react; stable false positive for this package. | ai |
Versions (showing 73 of 73)
| Version | Deps | Published |
|---|---|---|
| 20.73.0 | 25 / 14 | |
| 20.72.3 | 25 / 14 | |
| 20.72.2 | 25 / 14 | |
| 20.72.1 | 25 / 14 | |
| 20.71.1 | 25 / 14 | |
| 20.71.0 | 25 / 14 | |
| 20.70.0 | 26 / 15 | |
| 20.69.0 | 26 / 15 | |
| 20.68.0 | 26 / 15 | |
| 20.67.0 | 26 / 15 | |
| 20.66.6 | 28 / 14 | |
| 20.66.4 | 28 / 14 | |
| 20.66.2 | 28 / 14 | |
| 20.66.1 | 28 / 14 | |
| 20.66.0 | 28 / 14 | |
| 20.65.0 | 28 / 14 | |
| 20.64.0 | 28 / 14 | |
| 20.63.0 | 29 / 14 | |
| 20.61.1 | 29 / 14 | |
| 20.60.2 | 29 / 14 | |
| 20.60.1 | 29 / 14 | |
| 20.60.0 | 29 / 15 | |
| 20.59.1 | 29 / 15 | |
| 20.58.0 | 29 / 15 | |
| 20.57.1 | 29 / 15 | |
| 20.56.0 | 29 / 15 | |
| 20.55.2 | 29 / 15 | |
| 20.55.1 | 29 / 15 | |
| 20.55.0 | 29 / 15 | |
| 20.54.0 | 29 / 15 | |
| 20.53.1 | 29 / 15 | |
| 20.53.0 | 29 / 15 | |
| 20.51.0 | 29 / 15 | |
| 20.50.2 | 29 / 15 | |
| 20.50.1 | 29 / 15 | |
| 20.50.0 | 29 / 15 | |
| 20.49.4 | 29 / 15 | |
| 20.49.3 | 29 / 15 | |
| 20.49.2 | 29 / 15 | |
| 20.49.1 | 29 / 15 | |
| 20.49.0 | 29 / 15 | |
| 20.48.0 | 29 / 15 | |
| 20.47.1 | 29 / 15 | |
| 20.47.0 | 29 / 17 | |
| 20.46.0 | 29 / 20 | |
| 20.45.0 | 29 / 20 | |
| 20.43.1 | 29 / 20 | |
| 20.43.0 | 29 / 20 | |
| 20.42.1 | 29 / 20 | |
| 20.42.0 | 29 / 20 | |
| 20.41.0 | 29 / 20 | |
| 20.24.0 | 29 / 18 | |
| 20.23.0 | 29 / 18 | |
| 20.20.3 | 29 / 18 | |
| 20.20.0 | 29 / 18 | |
| 20.18.0 | 29 / 18 | |
| 20.16.0 | 29 / 18 | |
| 20.15.0 | 29 / 18 | |
| 20.14.2 | 29 / 18 | |
| 20.14.1 | 29 / 18 | |
| 20.14.0 | 29 / 18 | |
| 20.13.2 | 29 / 16 | |
| 20.13.0 | 29 / 16 | |
| 20.11.0 | 29 / 16 | |
| 20.10.0 | 29 / 16 | |
| 20.9.0 | 29 / 16 | |
| 20.8.1 | 29 / 16 | |
| 20.6.1 | 29 / 16 | |
| 20.5.0 | 29 / 16 | |
| 20.3.1 | 29 / 16 | |
| 20.2.0 | 29 / 16 | |
| 20.1.0 | 29 / 16 | |
| 20.0.0 | 29 / 16 |
v20.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.72.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.72.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.72.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.