@umbraco-ui/uui-base
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Umbraco org migrated publishing to GitHub Actions with SLSA attestation; transition is legitimate and expected to persist. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long dormancy followed by CI/CD-attested publish from official Umbraco org repo; consistent with a maintained monorepo release cycle. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.18.1 | 0 / 0 | |
| 1.18.0 | 0 / 0 | |
| 1.17.3 | 0 / 0 | |
| 1.17.2 | 0 / 0 | |
| 1.17.1 | 0 / 0 | |
| 1.17.0 | 0 / 0 | |
| 1.16.0 | 0 / 0 | |
| 1.15.0 | 0 / 0 | |
| 1.14.1 | 0 / 0 | |
| 1.14.0 | 0 / 0 | |
| 1.13.0 | 0 / 0 | |
| 1.12.2 | 0 / 0 | |
| 1.12.1 | 0 / 0 | |
| 1.12.0 | 0 / 0 | |
| 1.11.0 | 0 / 0 | |
| 1.10.0 | 0 / 0 | |
| 1.9.0 | 0 / 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.