@ukic/codemod
Codemod tool to help assist users upgrading from v2 to v3 of the UKIC design 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
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.2.15 | 3 / 4 | |
| 1.2.14 | 3 / 4 | |
| 1.2.13 | 3 / 4 | |
| 1.2.12 | 3 / 4 | |
| 1.2.9 | 3 / 4 | |
| 1.2.8 | 3 / 4 | |
| 1.2.7 | 3 / 4 | |
| 1.2.6 | 3 / 4 | |
| 1.2.5 | 3 / 4 | |
| 1.2.4 | 3 / 4 | |
| 1.2.3 | 3 / 4 | |
| 1.2.2 | 3 / 4 | |
| 1.2.1 | 3 / 4 | |
| 1.2.0 | 3 / 4 | |
| 1.1.0 | 3 / 4 |
v1.2.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gchq-dev-530) than the most recent previously approved version (gchq-developer-299a) on 2026-07-03, but gchq-dev-530 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.