@backstage/plugin-org-react
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Backstage monorepo plugin; description omitted by design, stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Backstage org publishes without Sigstore; not a security concern for this established package. | ai | |
| dependencies | unvetted-dep:@backstage/core-plugin-api | AI (dependencies): @backstage/core-plugin-api is a core dependency of the official Backstage framework; expected and legitimate for this package. | ai | |
| dependencies | unvetted-dep:@material-ui/lab | AI (dependencies): @material-ui/lab is a well-known, widely-used Material UI package; stable false positive for this Backstage plugin. | ai | |
| phantom-deps | phantom-dep:@backstage/catalog-client | AI (phantom-deps): Monorepo publishing pattern; @backstage/catalog-client is a same-org dep that may be used indirectly. Not a security concern. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-react | AI (dependencies): @backstage/plugin-catalog-react is a standard Backstage plugin dependency; expected and legitimate for this package. | ai | |
| dependencies | unvetted-dep:@material-ui/icons | AI (dependencies): @material-ui/icons is a well-known, widely-used Material UI package; stable false positive for this Backstage plugin. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.1.50 | 9 / 11 | |
| 0.1.49 | 9 / 11 | |
| 0.1.46 | 9 / 11 | |
| 0.1.45 | 9 / 11 | |
| 0.1.44 | 9 / 11 | |
| 0.1.43 | 9 / 11 | |
| 0.1.42 | 9 / 11 | |
| 0.1.39 | 9 / 11 |
v0.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.