@backstage/plugin-config-schema
A Backstage plugin that lets you browse the configuration schema of your app
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:zen-observable | AI (dependencies): zen-observable is a well-known observable utility used throughout the Backstage ecosystem; not a security risk. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): Official Backstage package from the backstage/backstage monorepo; stable ecosystem dependency. | ai | |
| dependencies | unvetted-dep:@material-ui/lab | AI (dependencies): Official Material-UI lab package; widely used in Backstage frontend plugins. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Official Backstage package from the backstage/backstage monorepo; stable ecosystem dependency. | ai | |
| dependencies | unvetted-dep:@material-ui/icons | AI (dependencies): Official Material-UI icons package; widely used in Backstage frontend plugins. | ai | |
| dependencies | unvetted-dep:@backstage/core-components | AI (dependencies): Official Backstage package from the backstage/backstage monorepo; stable ecosystem dependency. | ai | |
| dependencies | unvetted-dep:@backstage/core-plugin-api | AI (dependencies): Official Backstage package from the backstage/backstage monorepo; stable ecosystem dependency. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.1.79 | 10 / 9 | |
| 0.1.75 | 10 / 9 | |
| 0.1.73 | 10 / 9 | |
| 0.1.71 | 10 / 9 | |
| 0.1.70 | 10 / 9 | |
| 0.1.68 | 10 / 9 |
v0.1.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.