@backstage/plugin-mui-to-bui
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/ui | AI (dependencies): First-party Backstage monorepo package; legitimate dependency for a Backstage plugin in the @backstage scope. | ai | |
| dependencies | unvetted-dep:@backstage/theme | AI (dependencies): First-party Backstage monorepo package; legitimate dependency for a Backstage plugin in the @backstage scope. | ai | |
| dependencies | unvetted-dep:@backstage/core-plugin-api | AI (dependencies): First-party Backstage monorepo package; standard dependency for all Backstage frontend plugins. | ai | |
| dependencies | unvetted-dep:@backstage/frontend-plugin-api | AI (dependencies): First-party Backstage monorepo package; standard dependency for Backstage frontend plugins. | ai | |
| phantom-deps | phantom-dep:@backstage/theme | AI (phantom-deps): Common pattern in Backstage plugins; theme types used transitively. Same org scope, no security concern. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.2.7 | 6 / 9 | |
| 0.2.6 | 6 / 9 | |
| 0.2.5 | 6 / 9 | |
| 0.2.4 | 6 / 9 | |
| 0.2.3 | 6 / 9 | |
| 0.2.2 | 6 / 9 | |
| 0.2.1 | 7 / 9 | |
| 0.2.0 | 7 / 9 |
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.