@red-hat-developer-hub/backstage-plugin-dynamic-home-page Apache-2.0 32 versions

@red-hat-developer-hub/backstage-plugin-dynamic-home-page

npm Repository

32

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@backstage/plugin-home-react	AI (phantom-deps): Backstage plugin config reference; stable pattern for this package.	ai	2026/05/12
bogus-package	bogus-package	AI (bogus-package): Internal plugin with minimal README; not indicative of spam in Red Hat's ecosystem.	ai	2026/05/12
phantom-deps	phantom-dep:@mui/styles	AI (phantom-deps): MUI styles referenced in config files for Backstage plugin theming; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@backstage/theme	AI (phantom-deps): Backstage theme referenced in config files; stable false positive for this plugin package.	ai	2026/04/30
phantom-deps	phantom-dep:@backstage/catalog-model	AI (phantom-deps): Catalog model referenced in config files; stable false positive for this Backstage plugin.	ai	2026/04/30
phantom-deps	phantom-dep:@backstage/catalog-client	AI (phantom-deps): Catalog client referenced in config files; stable false positive for this Backstage plugin.	ai	2026/04/30

Versions (showing 32 of 32)

Version	Deps	Published
1.13.4	20 / 16	2026-05-27
1.13.2	20 / 16	2026-05-19
1.13.1	20 / 16	2026-05-05
1.13.0	20 / 16	2026-04-28
1.12.0	18 / 16	2026-04-15
1.11.0	18 / 16	2026-03-30
1.10.6	17 / 13	2026-02-06
1.10.5	17 / 13	2026-01-30
1.10.4	17 / 13	2026-01-23
1.10.3	17 / 13	2026-01-13
1.10.2	17 / 13	2025-12-09
1.10.1	17 / 13	2025-12-09
1.10.0	17 / 13	2025-12-09
1.9.4	17 / 13	2025-12-09
1.9.3	17 / 13	2025-12-03
1.9.2	17 / 13	2025-10-08
1.9.1	17 / 13	2025-10-02
1.9.0	17 / 13	2025-09-30
1.8.0	17 / 13	2025-09-25
1.7.0	17 / 13	2025-09-11
1.6.0	17 / 13	2025-08-21
1.5.5	17 / 13	2025-08-21
1.5.4	17 / 13	2025-08-02
1.5.3	17 / 13	2025-07-25
1.5.2	17 / 13	2025-07-23
1.5.0	17 / 13	2025-06-13
1.4.2	17 / 13	2025-06-06
1.4.1	17 / 13	2025-05-26
1.4.0	17 / 13	2025-05-26
1.3.3	13 / 13	2025-05-12
1.3.2	13 / 13	2025-05-08
1.3.1	13 / 13	2025-05-01

v1.13.4

1 finding

LOW No provenance attestation provenance

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

v1.13.2

1 finding

LOW No provenance attestation provenance

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

v1.13.1

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

1 finding

LOW No provenance attestation provenance

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

v1.10.5

1 finding

LOW No provenance attestation provenance

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

v1.10.4

1 finding

LOW No provenance attestation provenance

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

v1.10.3

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

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

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

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

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

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

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

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