@backstage/plugin-app-react
5
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
patrikofrebenmarcuseide
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; short README and no keywords are standard for @backstage org packages that document via the root repo. | ai | |
| phantom-deps | phantom-dep:@backstage/core-plugin-api | AI (phantom-deps): Same-org dependency declared but used transitively/re-exported; common pattern in Backstage plugin packages. | ai | |
| phantom-deps | phantom-dep:@material-ui/core | AI (phantom-deps): MUI v4 is declared as a runtime dep and referenced in config; phantom detection is a false positive for this package's usage pattern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 3 / 9 | |
| 0.2.2 | 3 / 9 | |
| 0.2.1 | 3 / 9 | |
| 0.2.0 | 3 / 9 | |
| 0.1.0 | 3 / 9 |
v0.2.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.