@red-hat-developer-hub/backstage-plugin-orchestrator-form-react
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@backstage/core-plugin-api | AI (phantom-deps): Declared as a dep and used transitively; phantom-dep heuristic fires on config-file references, stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse README is typical for internal Red Hat plugin packages in this monorepo; not indicative of spam. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 2.8.4 | 14 / 8 | |
| 2.8.3 | 14 / 8 | |
| 2.8.2 | 14 / 8 | |
| 2.8.1 | 14 / 8 | |
| 2.8.0 | 14 / 8 | |
| 2.7.0 | 14 / 8 | |
| 2.6.3 | 14 / 8 | |
| 2.6.2 | 14 / 8 | |
| 2.6.1 | 14 / 8 | |
| 2.6.0 | 14 / 8 | |
| 2.5.8 | 14 / 8 | |
| 2.5.7 | 14 / 8 | |
| 2.5.6 | 14 / 8 | |
| 2.5.5 | 14 / 8 | |
| 2.5.4 | 14 / 8 | |
| 2.5.3 | 14 / 8 | |
| 2.5.2 | 14 / 8 | |
| 2.5.1 | 14 / 8 | |
| 2.5.0 | 14 / 8 | |
| 2.4.0 | 14 / 8 | |
| 2.3.1 | 13 / 9 | |
| 2.3.0 | 13 / 9 | |
| 2.2.0 | 13 / 9 | |
| 2.1.0 | 13 / 8 | |
| 2.0.6 | 13 / 8 | |
| 2.0.5 | 13 / 8 | |
| 2.0.4 | 13 / 8 | |
| 2.0.3 | 13 / 8 | |
| 2.0.2 | 13 / 8 | |
| 2.0.1 | 13 / 8 | |
| 2.0.0 | 13 / 8 |
v2.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.