@red-hat-developer-hub/backstage-plugin-orchestrator-backend Apache-2.0 31 versions

@red-hat-developer-hub/backstage-plugin-orchestrator-backend

npm Repository Homepage

31

Versions

Apache-2.0

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 — the axios compromise (March 2026) relied on exactly this gap.

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
phantom-deps	phantom-dep:@backstage/backend-tasks	AI (phantom-deps): Same monorepo/dynamic-plugin pattern; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:cloudevents	AI (phantom-deps): Config-referenced Backstage framework dependency; stable pattern for this plugin.	ai	2026/05/15
phantom-deps	phantom-dep:@backstage/errors	AI (phantom-deps): Config-referenced Backstage framework dependency; stable pattern for this plugin.	ai	2026/05/15
phantom-deps	phantom-dep:@backstage/core-plugin-api	AI (phantom-deps): Backstage monorepo plugin; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:@backstage/plugin-scaffolder-node	AI (phantom-deps): Backstage monorepo plugin; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:yn	AI (phantom-deps): yn is a legitimate runtime dep used via config; phantom-dep heuristic misfires on bundled backend plugins.	ai	2026/05/15
bogus-package	bogus-package	AI (bogus-package): Established RHDH plugin with thin README typical of monorepo workspace packages; not spam.	ai	2026/05/15
phantom-deps	phantom-dep:@backstage/plugin-scaffolder-backend	AI (phantom-deps): Backstage monorepo plugin; stable false positive for this package.	ai	2026/05/15
phantom-deps	phantom-dep:express-promise-router	AI (phantom-deps): express-promise-router is a declared runtime dep; phantom-dep heuristic misfires on bundled output.	ai	2026/05/15
phantom-deps	phantom-dep:@backstage/catalog-client	AI (phantom-deps): Backstage monorepo plugin; import may be indirect through re-exports. Stable false positive.	ai	2026/05/15

Versions (showing 31 of 31)

Version	Deps	Published
8.9.5	26 / 10	2026-06-02
8.9.4	26 / 10	2026-05-05
8.9.3	26 / 10	2026-05-05
8.9.2	26 / 10	2026-04-29
8.9.1	26 / 10	2026-04-20
8.9.0	26 / 10	2026-04-17
8.8.2	24 / 10	2026-04-15
8.8.1	24 / 10	2026-04-15
8.8.0	24 / 10	2026-04-14
8.7.3	24 / 10	2026-04-09
8.7.2	24 / 10	2026-03-11
8.7.1	24 / 10	2026-02-16
8.7.0	24 / 10	2026-02-16
8.6.7	24 / 10	2026-04-21
8.6.6	24 / 10	2026-04-17
8.6.5	24 / 10	2026-04-17
8.6.4	24 / 10	2026-04-09
8.6.3	24 / 10	2026-03-12
8.6.2	24 / 10	2026-03-09
8.6.1	24 / 10	2026-02-11
8.6.0	24 / 10	2026-01-16
8.5.1	23 / 10	2026-01-07
8.5.0	23 / 10	2025-12-04
8.4.0	23 / 9	2025-10-30
8.3.1	23 / 9	2026-04-08
8.3.0	23 / 9	2025-10-24
8.2.0	24 / 9	2025-10-14
8.0.3	24 / 9	2025-08-12
8.0.2	24 / 9	2025-08-06
8.0.1	24 / 9	2025-07-31
8.0.0	24 / 9	2025-07-29

v8.9.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.9.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.9.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.9.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.8.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.8.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.7.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.7.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.6.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.6.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.6.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.6.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.6.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.6.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.