@backstage-community/plugin-linguist-backend
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:express | AI (phantom-deps): Backstage backend plugins declare express as a runtime dep by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:express-promise-router | AI (phantom-deps): Same Backstage backend convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): Declared for compatibility; stable false positive for this plugin. | ai | |
| phantom-deps | phantom-dep:yn | AI (phantom-deps): Config utility declared by convention in Backstage plugins; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Type-only framework dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Backstage config schema dep; loaded by framework convention, stable false positive. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-catalog-node | AI (phantom-deps): Backstage catalog integration dep; stable false positive for this plugin. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.28.0 | 20 / 11 | |
| 0.27.0 | 20 / 11 | |
| 0.26.0 | 20 / 11 | |
| 0.25.0 | 20 / 11 | |
| 0.24.0 | 20 / 11 | |
| 0.23.0 | 20 / 11 | |
| 0.22.0 | 20 / 11 | |
| 0.21.1 | 20 / 11 | |
| 0.21.0 | 20 / 11 | |
| 0.20.1 | 20 / 11 | |
| 0.20.0 | 20 / 12 | |
| 0.19.0 | 20 / 12 | |
| 0.18.0 | 20 / 12 | |
| 0.17.0 | 20 / 12 | |
| 0.16.0 | 20 / 12 | |
| 0.15.0 | 20 / 12 | |
| 0.14.1 | 20 / 13 | |
| 0.14.0 | 20 / 13 | |
| 0.13.0 | 20 / 12 | |
| 0.12.0 | 20 / 9 | |
| 0.11.1 | 20 / 9 | |
| 0.11.0 | 20 / 9 | |
| 0.10.0 | 20 / 9 | |
| 0.9.0 | 19 / 8 | |
| 0.8.0 | 19 / 8 | |
| 0.7.0 | 19 / 8 | |
| 0.6.4 | 21 / 8 | |
| 0.6.3 | 21 / 8 | |
| 0.6.2 | 21 / 8 | |
| 0.6.1 | 21 / 8 | |
| 0.6.0 | 21 / 8 | |
| 0.5.23 | 21 / 8 | |
| 0.5.22 | 21 / 8 | |
| 0.5.21 | 21 / 8 | |
| 0.5.20 | 20 / 8 | |
| 0.5.19 | 20 / 8 | |
| 0.5.17 | 20 / 8 |
v0.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.