@backstage/plugin-scaffolder-backend-module-notifications Apache-2.0 13 versions

@backstage/plugin-scaffolder-backend-module-notifications

npm Repository

The notifications backend module for the scaffolder plugin.

13

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
bogus-package	bogus-package	AI (bogus-package): Backstage monorepo plugin modules routinely have short READMEs and no keywords; this is a structural pattern of the project, not a spam indicator.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/plugin-notifications-common	AI (phantom-deps): Monorepo packages commonly declare deps that are used transitively or re-exported; same org scope confirms legitimacy.	ai	2026/04/25

Versions (showing 13 of 13)

Version	Deps	Published
0.1.22	5 / 2	2026-05-19
0.1.21	5 / 2	2026-04-14
0.1.20	5 / 2	2026-03-17
0.1.19	5 / 2	2026-02-17
0.1.18	5 / 2	2026-01-20
0.1.17	5 / 2	2025-12-16
0.1.16	5 / 2	2025-11-18
0.1.15	5 / 2	2025-10-14
0.1.14	5 / 2	2025-09-16
0.1.13	5 / 2	2025-08-19
0.1.12	5 / 2	2025-07-15
0.1.11	5 / 2	2025-06-17
0.1.10	6 / 2	2025-05-20

v0.1.22

1 finding

LOW No provenance attestation provenance

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

v0.1.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.1.20

1 finding

LOW No provenance attestation provenance

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

v0.1.19

1 finding

LOW No provenance attestation provenance

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

v0.1.18

1 finding

LOW No provenance attestation provenance

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

v0.1.17

1 finding

LOW No provenance attestation provenance

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

v0.1.16

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

1 finding

LOW No provenance attestation provenance

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

v0.1.14

1 finding

LOW No provenance attestation provenance

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

v0.1.13

1 finding

LOW No provenance attestation provenance

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

v0.1.12

1 finding

LOW No provenance attestation provenance

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

v0.1.11

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

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.