@backstage/plugin-signals Apache-2.0 10 versions

@backstage/plugin-signals

npm Repository

10

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

patrikofrebenmarcuseide

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:react-use	AI (phantom-deps): Backstage build tooling pattern; declared deps not directly imported is normal for this monorepo plugin.	ai	2026/05/09
phantom-deps	phantom-dep:@material-ui/lab	AI (phantom-deps): Standard MUI v4 dep in Backstage plugins; referenced via build config, not a real phantom.	ai	2026/05/09
phantom-deps	phantom-dep:@material-ui/icons	AI (phantom-deps): Standard MUI v4 dep in Backstage plugins; referenced via build config, not a real phantom.	ai	2026/05/09
dependencies	unvetted-dep:@material-ui/lab	AI (dependencies): MUI v4 lab is a well-known, widely-used package across the Backstage ecosystem.	ai	2026/05/09
phantom-deps	phantom-dep:@material-ui/core	AI (phantom-deps): Referenced in config files as noted; standard for Backstage plugins using MUI v4 theming.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/core-components	AI (phantom-deps): Expected in Backstage frontend plugins; may be used indirectly or declared for compatibility reasons within the monorepo.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/theme	AI (phantom-deps): Expected in Backstage frontend plugins; may be used indirectly via theming infrastructure or declared for config purposes.	ai	2026/04/25

Versions (showing 10 of 10)

Version	Deps	Published
0.0.31	8 / 11	2026-05-19
0.0.30	9 / 11	2026-04-14
0.0.29	8 / 11	2026-03-17
0.0.28	8 / 11	2026-02-17
0.0.27	8 / 11	2026-01-20
0.0.26	8 / 11	2025-12-16
0.0.25	9 / 11	2025-11-18
0.0.21	12 / 13	2025-07-15
0.0.20	11 / 13	2025-06-17
0.0.19	11 / 13	2025-05-20

v0.0.31

1 finding

LOW No provenance attestation provenance

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

v0.0.30

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.

v0.0.29

1 finding

LOW No provenance attestation provenance

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

v0.0.28

1 finding

LOW No provenance attestation provenance

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

v0.0.27

1 finding

LOW No provenance attestation provenance

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

v0.0.26

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.

v0.0.25

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.

v0.0.21

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.

v0.0.20

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.

v0.0.19

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.