@gitlab/ui
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:echarts | AI (phantom-deps): Optional/conditional dep referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:gridstack | AI (phantom-deps): Optional/conditional dep referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@floating-ui/dom | AI (phantom-deps): Optional/conditional dep referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:vue-runtime-helpers | AI (phantom-deps): Optional/conditional dep referenced in config; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @gitlab/ui is the official GitLab UI library; not a typosquat of yup. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @gitlab/ui is the official GitLab UI library; not a typosquat of uuid. | ai | |
| phantom-deps | phantom-dep:iframe-resizer | AI (phantom-deps): iframe-resizer is a declared runtime dependency; may be used indirectly via dynamic import or config. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @gitlab/ui is the official GitLab UI library; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @gitlab/ui is the official GitLab UI library; not a typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @gitlab/ui is the official GitLab UI library; not a typosquat of joi. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 134.2.0 | 9 / 88 | |
| 134.1.3 | 9 / 87 | |
| 134.1.2 | 9 / 87 | |
| 134.1.1 | 9 / 87 | |
| 134.1.0 | 9 / 87 | |
| 134.0.0 | 9 / 87 | |
| 133.0.0 | 9 / 87 | |
| 132.2.2 | 9 / 87 | |
| 132.2.1 | 9 / 87 | |
| 132.2.0 | 9 / 87 | |
| 132.1.0 | 9 / 86 | |
| 132.0.3 | 9 / 86 | |
| 132.0.2 | 9 / 86 | |
| 132.0.1 | 9 / 86 |
v134.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v134.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v134.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v134.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v134.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v134.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v133.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v132.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v132.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v132.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v132.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v132.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v132.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v132.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.