@backstage/plugin-home-react
A Backstage plugin that contains react components helps you build a home page
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:@material-ui/icons | AI (dependencies): Well-known Material-UI icons package; expected dependency for a Backstage UI plugin. No security concern. | ai | |
| dependencies | unvetted-dep:@backstage/core-compat-api | AI (dependencies): Official Backstage core package from the same org scope; expected dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/core-components | AI (dependencies): Official Backstage core package from the same org scope; expected dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/core-plugin-api | AI (dependencies): Official Backstage core package from the same org scope; expected dependency for this plugin. | ai | |
| dependencies | unvetted-dep:@backstage/frontend-plugin-api | AI (dependencies): Official Backstage core package from the same org scope; expected dependency for this plugin. | ai | |
| phantom-deps | phantom-dep:@backstage/core-compat-api | AI (phantom-deps): Same org scope; declared for compatibility shim purposes in Backstage plugins even when not directly imported. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.1.38 | 7 / 6 | |
| 0.1.37 | 7 / 6 | |
| 0.1.36 | 7 / 6 | |
| 0.1.35 | 7 / 6 | |
| 0.1.34 | 6 / 6 | |
| 0.1.33 | 6 / 6 | |
| 0.1.32 | 6 / 6 | |
| 0.1.31 | 6 / 6 | |
| 0.1.30 | 6 / 6 | |
| 0.1.29 | 6 / 6 | |
| 0.1.28 | 6 / 6 | |
| 0.1.27 | 6 / 6 | |
| 0.1.26 | 5 / 6 |
v0.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.