@red-hat-developer-hub/backstage-plugin-orchestrator-common
28
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
nickboldtbethany.griggskashish_mittaltomaskralrhdh-botschultzp2020
Keywords
backstagepluginorchestratorworkflows
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established Red Hat plugin with 43 versions; sparse README is a documentation gap, not a spam/malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Red Hat org package with public GitHub repo; lack of Sigstore provenance is common and not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:@backstage/core-plugin-api | AI (phantom-deps): Backstage plugin APIs are often referenced in config/metadata rather than direct imports; stable pattern for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo-published library; description omission is common and not indicative of malice in established packages. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 3.8.0 | 6 / 5 | |
| 3.7.3 | 6 / 5 | |
| 3.7.2 | 6 / 5 | |
| 3.7.1 | 6 / 5 | |
| 3.7.0 | 6 / 5 | |
| 3.6.4 | 6 / 5 | |
| 3.6.3 | 6 / 5 | |
| 3.6.2 | 6 / 5 | |
| 3.6.1 | 6 / 5 | |
| 3.6.0 | 6 / 5 | |
| 3.5.3 | 6 / 5 | |
| 3.5.2 | 6 / 5 | |
| 3.5.1 | 6 / 5 | |
| 3.5.0 | 6 / 5 | |
| 3.4.5 | 5 / 5 | |
| 3.4.4 | 5 / 5 | |
| 3.4.3 | 5 / 5 | |
| 3.4.2 | 5 / 5 | |
| 3.4.1 | 5 / 5 | |
| 3.4.0 | 6 / 5 | |
| 3.3.1 | 6 / 5 | |
| 3.3.0 | 6 / 4 | |
| 3.2.0 | 6 / 4 | |
| 3.0.6 | 6 / 4 | |
| 3.0.4 | 5 / 4 | |
| 3.0.3 | 5 / 4 | |
| 3.0.2 | 4 / 5 | |
| 3.0.1 | 4 / 5 |
v3.8.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.2
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.