@backstage/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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@base-ui-components/react | AI (dependencies): @base-ui-components/react is the official MUI Base UI library; alpha versioning is expected for this package. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): UI library; deps referenced in build/config files, not direct imports. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@base-ui-components/react | AI (phantom-deps): UI library; deps referenced in build/config files, not direct imports. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-aria-components | AI (phantom-deps): UI library; deps referenced in build/config files, not direct imports. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@remixicon/react | AI (phantom-deps): UI library; deps referenced in build/config files, not direct imports. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:motion | AI (phantom-deps): UI library; deps referenced in build/config files, not direct imports. Stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@remixicon/react | AI (dependencies): @remixicon/react is a legitimate, widely-used icon library; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tanstack/react-table | AI (phantom-deps): Likely re-exported or used indirectly via type declarations; stable pattern for this UI library. | ai | |
| phantom-deps | phantom-dep:@react-types/calendar | AI (phantom-deps): Type-only dependency used in config/type declarations; not directly imported in runtime code is expected for @react-types/* packages. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @backstage/ui is the legitimate Backstage UI library, not a typosquat of joi. Levenshtein match on scoped package name vs short unrelated package is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @backstage/ui is the legitimate Backstage UI library, not a typosquat of qs. Levenshtein match on scoped package name vs short unrelated package is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @backstage/ui is the legitimate Backstage UI library, not a typosquat of pg. Levenshtein match on scoped package name vs short unrelated package is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @backstage/ui is the legitimate Backstage UI library, not a typosquat of yup. Levenshtein match on scoped package name vs short unrelated package is a false positive. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @backstage/ui is the legitimate Backstage UI library, not a typosquat of uuid. Levenshtein match on scoped package name vs short unrelated package is a false positive. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 11 / 15 | |
| 0.14.3 | 8 / 11 | |
| 0.14.2 | 8 / 11 | |
| 0.14.1 | 8 / 11 | |
| 0.14.0 | 11 / 11 | |
| 0.13.3 | 11 / 11 | |
| 0.13.2 | 6 / 11 | |
| 0.13.1 | 6 / 11 | |
| 0.13.0 | 6 / 11 | |
| 0.12.1 | 5 / 10 | |
| 0.12.0 | 5 / 10 | |
| 0.11.3 | 5 / 13 | |
| 0.11.2 | 5 / 13 | |
| 0.11.1 | 5 / 13 | |
| 0.11.0 | 5 / 13 | |
| 0.10.1 | 4 / 13 | |
| 0.10.0 | 4 / 13 | |
| 0.9.2 | 4 / 13 | |
| 0.9.1 | 4 / 13 | |
| 0.9.0 | 4 / 13 | |
| 0.8.2 | 5 / 13 | |
| 0.8.1 | 5 / 13 | |
| 0.8.0 | 5 / 13 | |
| 0.7.1 | 5 / 13 | |
| 0.6.1 | 6 / 21 | |
| 0.6.0 | 6 / 21 |
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.