@red-hat-developer-hub/backstage-plugin-global-header Apache-2.0 40 versions

@red-hat-developer-hub/backstage-plugin-global-header

npm Repository

40

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

backstageplugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): rhdh-bot is Red Hat's CI automation account; publisher transitions to this bot are expected for this package family.	ai	2026/05/09
maintainer-change	maintainer-added	AI (maintainer-change): rhdh-bot and schultzp2020 are Red Hat org members; addition consistent with team maintenance practices.	ai	2026/05/09
bogus-package	bogus-package	AI (bogus-package): Backstage plugin with minimal README; not indicative of spam or malice for this established package.	ai	2026/05/09
dependencies	unvetted-dep:@scalprum/react-core	AI (dependencies): @scalprum/react-core is a Red Hat OpenShift console library; its use is expected in RHDH plugins.	ai	2026/04/28
phantom-deps	phantom-dep:@backstage/plugin-search-common	AI (phantom-deps): Backstage plugin declares deps in config files; phantom-dep false positive for this package.	ai	2026/04/28
phantom-deps	phantom-dep:@backstage/plugin-search-backend	AI (phantom-deps): Backstage plugin declares deps in config files; phantom-dep false positive for this package.	ai	2026/04/28
phantom-deps	phantom-dep:@backstage/plugin-notifications-common	AI (phantom-deps): Backstage plugin declares deps in config files; phantom-dep false positive for this package.	ai	2026/04/28
phantom-deps	phantom-dep:react-use	AI (phantom-deps): Backstage plugin declares deps in config files; phantom-dep false positive for this package.	ai	2026/04/28
phantom-deps	phantom-dep:@backstage/plugin-search-backend-module-catalog	AI (phantom-deps): Backstage plugin declares deps in config files; phantom-dep false positive for this package.	ai	2026/04/28
phantom-deps	phantom-dep:@backstage/plugin-search-backend-module-techdocs	AI (phantom-deps): Backstage plugin declares deps in config files; phantom-dep false positive for this package.	ai	2026/04/28
phantom-deps	phantom-dep:@backstage/plugin-search-backend-module-pg	AI (phantom-deps): Backstage plugin declares deps in config files; phantom-dep false positive for this package.	ai	2026/04/28
phantom-deps	phantom-dep:@backstage/theme	AI (phantom-deps): Backstage plugin declares deps in config files; phantom-dep false positive for this package.	ai	2026/04/28
phantom-deps	phantom-dep:@mui/styled-engine	AI (phantom-deps): Backstage plugin declares deps in config files; phantom-dep false positive for this package.	ai	2026/04/28
phantom-deps	phantom-dep:@backstage/plugin-search	AI (phantom-deps): Backstage plugin declares deps in config files; phantom-dep false positive for this package.	ai	2026/04/28

Versions (showing 40 of 40)

Version	Deps	Published
1.21.5	23 / 16	2026-05-18
1.21.4	23 / 16	2026-05-06
1.21.3	23 / 16	2026-05-05
1.21.2	23 / 16	2026-05-05
1.21.1	23 / 16	2026-04-25
1.21.0	23 / 16	2026-04-23
1.20.3	21 / 16	2026-03-27
1.20.2	21 / 16	2026-03-04
1.20.1	21 / 15	2026-01-13
1.20.0	21 / 15	2025-12-09
1.19.0	21 / 15	2025-11-11
1.18.2	21 / 15	2025-11-10
1.18.1	21 / 15	2025-10-09
1.18.0	21 / 15	2025-10-07
1.17.3	21 / 15	2025-09-26
1.17.2	21 / 15	2025-09-24
1.17.1	21 / 15	2025-09-12
1.17.0	21 / 15	2025-09-11
1.16.1	21 / 15	2025-09-10
1.16.0	21 / 15	2025-09-09
1.15.1	21 / 15	2025-08-21
1.15.0	21 / 15	2025-08-07
1.14.1	21 / 15	2025-07-21
1.14.0	21 / 15	2025-07-07
1.13.0	21 / 15	2025-07-01
1.12.0	21 / 15	2025-07-01
1.11.2	21 / 15	2025-06-25
1.11.1	21 / 15	2025-06-23
1.11.0	21 / 15	2025-06-20
1.10.1	21 / 15	2025-06-16
1.9.0	21 / 15	2025-06-04
1.8.0	21 / 15	2025-06-03
1.7.3	21 / 14	2025-06-02
1.7.2	21 / 14	2025-05-26
1.7.1	21 / 14	2025-05-19
1.7.0	21 / 14	2025-05-09
1.6.0	21 / 14	2025-05-07
1.5.2	21 / 14	2025-05-20
1.5.1	21 / 14	2025-05-06
1.0.1	21 / 14	2025-05-21

v1.21.5

1 finding

LOW No provenance attestation provenance

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

v1.21.4

1 finding

LOW No provenance attestation provenance

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

v1.21.3

1 finding

LOW No provenance attestation provenance

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

v1.21.2

1 finding

LOW No provenance attestation provenance

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

v1.21.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.

v1.21.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.

v1.20.3

1 finding

LOW No provenance attestation provenance

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

v1.20.2

1 finding

LOW No provenance attestation provenance

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

v1.20.1

1 finding

LOW No provenance attestation provenance

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

v1.20.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.

v1.19.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.

v1.18.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.

v1.18.1

2 findings

HIGH Publisher changed: kashish_mittal → rhdh-bot (on 2025-10-09) provenance

This version was published by a different npm account than previous versions on 2025-10-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.18.0

2 findings

HIGH Publisher changed: kashish_mittal → rhdh-bot (on 2025-10-07) provenance

This version was published by a different npm account than previous versions on 2025-10-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.17.3

2 findings

HIGH Publisher changed: kashish_mittal → rhdh-bot (on 2025-09-26) provenance

This version was published by a different npm account than previous versions on 2025-09-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.17.2

2 findings

HIGH Publisher changed: kashish_mittal → rhdh-bot (on 2025-09-24) provenance

This version was published by a different npm account than previous versions on 2025-09-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.17.1

2 findings

HIGH Publisher changed: kashish_mittal → rhdh-bot (on 2025-09-12) provenance

This version was published by a different npm account than previous versions on 2025-09-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.17.0

2 findings

HIGH Publisher changed: kashish_mittal → rhdh-bot (on 2025-09-11) provenance

This version was published by a different npm account than previous versions on 2025-09-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.16.1

2 findings

HIGH Publisher changed: kashish_mittal → rhdh-bot (on 2025-09-10) provenance

This version was published by a different npm account than previous versions on 2025-09-10. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.16.0

2 findings

HIGH Publisher changed: kashish_mittal → rhdh-bot (on 2025-09-09) provenance

This version was published by a different npm account than previous versions on 2025-09-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.15.1

2 findings

HIGH Publisher changed: kashish_mittal → rhdh-bot (on 2025-08-21) provenance

This version was published by a different npm account than previous versions on 2025-08-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.15.0

2 findings

HIGH Publisher changed: kashish_mittal → rhdh-bot (on 2025-08-07) provenance

This version was published by a different npm account than previous versions on 2025-08-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.14.1

1 finding

LOW No provenance attestation provenance

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

v1.14.0

1 finding

LOW No provenance attestation provenance

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

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.2

1 finding

LOW No provenance attestation provenance

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

v1.11.1

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.1

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

LOW No provenance attestation provenance

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

v1.7.3

1 finding

LOW No provenance attestation provenance

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

v1.7.2

1 finding

LOW No provenance attestation provenance

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

v1.7.1

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.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.

v1.5.2

1 finding

LOW No provenance attestation provenance

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

v1.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.

v1.0.1

1 finding

LOW No provenance attestation provenance

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