@backstage/plugin-permission-backend
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Same-org monorepo package, expected pattern. | ai | |
| phantom-deps | phantom-dep:yn | AI (phantom-deps): Used via config convention in Backstage backend plugins, stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Type-only package loaded by convention, expected for express backend. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Backstage monorepo packages consistently lack per-package keywords/descriptions/README code blocks; this is a structural monorepo pattern, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Backstage monorepo packages omit per-package descriptions; documentation lives in the central repo. Not a malware signal for this well-established package. | ai | |
| provenance | no-provenance | AI (provenance): Backstage has not adopted Sigstore provenance attestation across its release pipeline; absence is consistent with all prior versions of this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.7.14 | 11 / 8 | |
| 0.7.13 | 11 / 8 | |
| 0.7.12 | 11 / 8 | |
| 0.7.11 | 12 / 8 | |
| 0.7.10 | 12 / 8 | |
| 0.7.9 | 12 / 8 | |
| 0.7.8 | 12 / 8 | |
| 0.7.7 | 12 / 8 | |
| 0.7.6 | 12 / 8 | |
| 0.7.5 | 12 / 8 | |
| 0.7.4 | 12 / 8 | |
| 0.7.3 | 12 / 8 | |
| 0.7.2 | 12 / 8 | |
| 0.7.1 | 12 / 8 | |
| 0.7.0 | 12 / 8 | |
| 0.6.0 | 14 / 7 |
v0.7.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.