@backstage/plugin-auth
7
Versions
Apache-2.0
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@material-ui/lab | AI (dependencies): @material-ui/lab 4.0.0-alpha.61 is the standard MUI v4 lab companion; its alpha pin is conventional for MUI v4 projects and poses no real risk. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package under the official @backstage org; missing description is a metadata gap, not a malware signal. | ai | |
| phantom-deps | phantom-dep:@backstage/theme | AI (phantom-deps): @backstage/theme is a legitimate same-org dependency; phantom detection likely reflects indirect usage through other @backstage packages. | ai | |
| provenance | no-provenance | AI (provenance): Established @backstage monorepo package with 182 versions; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.1.8 | 6 / 12 | |
| 0.1.7 | 6 / 12 | |
| 0.1.6 | 6 / 12 | |
| 0.1.4 | 8 / 12 | |
| 0.1.3 | 8 / 12 | |
| 0.1.2 | 8 / 12 | |
| 0.1.0 | 8 / 12 |
v0.1.8
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
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.
v0.1.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.