@umbraco-ui/uui-ref-node-data-type
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.18.1 | 2 / 0 | |
| 1.18.0 | 2 / 0 | |
| 1.17.3 | 2 / 0 | |
| 1.17.2 | 2 / 0 | |
| 1.17.1 | 2 / 0 | |
| 1.17.0 | 2 / 0 | |
| 1.16.0 | 2 / 0 | |
| 1.15.0 | 2 / 0 | |
| 1.14.1 | 2 / 0 | |
| 1.14.0 | 2 / 0 | |
| 1.13.0 | 2 / 0 | |
| 1.12.2 | 2 / 0 | |
| 1.12.1 | 2 / 0 | |
| 1.12.0 | 2 / 0 | |
| 1.11.0 | 2 / 0 | |
| 1.10.0 | 2 / 0 | |
| 1.9.0 | 2 / 0 |
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.