@red-hat-developer-hub/backstage-plugin-x2a-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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Red Hat org package; no provenance is consistent across all versions and not a malware indicator here. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Org-published Backstage plugin; missing description is a cosmetic issue, not a risk indicator for this package. | ai | |
| dependencies | unvetted-dep:@red-hat-developer-hub/backstage-plugin-x2a-common | AI (dependencies): Sibling package from the same Red Hat monorepo; expected dependency for this plugin suite. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-catalog-backend | AI (phantom-deps): Same Backstage workspace pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/backend-defaults | AI (phantom-deps): Backstage workspace plugin; peer/config deps declared but not directly imported is standard pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-auth-backend | AI (phantom-deps): Same Backstage workspace pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-auth-backend-module-guest-provider | AI (phantom-deps): Same Backstage workspace pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-auth-backend-module-github-provider | AI (phantom-deps): Same Backstage workspace pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:express-promise-router | AI (phantom-deps): Backstage backend plugin pattern; router may be referenced indirectly via framework wiring. | ai | |
| phantom-deps | phantom-dep:@backstage/catalog-client | AI (phantom-deps): Common Backstage backend plugin pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): Backstage monorepo pattern; types used in config/type declarations, not direct imports. | ai | |
| phantom-deps | phantom-dep:@backstage/catalog-model | AI (phantom-deps): Common Backstage type-only usage in config files; stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.6.0 | 16 / 10 | |
| 1.5.0 | 16 / 10 | |
| 1.4.2 | 16 / 10 | |
| 1.4.1 | 16 / 10 | |
| 1.4.0 | 16 / 10 | |
| 1.3.1 | 14 / 11 | |
| 1.3.0 | 14 / 11 | |
| 1.2.0 | 19 / 7 | |
| 1.1.0 | 19 / 7 | |
| 1.0.1 | 18 / 7 | |
| 1.0.0 | 18 / 7 |
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.