@backstage/plugin-notifications-node No license 38 versions

@backstage/plugin-notifications-node

npm Repository

38

Versions

—

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

patrikofrebenmarcuseide

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:knex	AI (phantom-deps): knex is a legitimate declared dependency in this Backstage monorepo package; phantom-dep fires due to indirect/config usage, not a real risk.	ai	2026/04/25
phantom-deps	phantom-dep:uuid	AI (phantom-deps): uuid is a legitimate declared dependency; phantom-dep fires due to indirect usage pattern common in monorepo packages.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/catalog-model	AI (phantom-deps): Same-org Backstage package declared as dependency; phantom-dep is a false positive for monorepo indirect usage.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/catalog-client	AI (phantom-deps): Same-org Backstage package declared as dependency; phantom-dep is a false positive for monorepo indirect usage.	ai	2026/04/25
phantom-deps	phantom-dep:@backstage/plugin-signals-node	AI (phantom-deps): Same-org Backstage package declared as dependency; phantom-dep is a false positive for monorepo indirect usage.	ai	2026/04/25

Versions (showing 38 of 38)

Version	Deps	Published
0.2.28	2 / 4	2026-07-14
0.2.27	2 / 4	2026-06-16
0.2.26	2 / 4	2026-05-19
0.2.25	7 / 4	2026-04-14
0.2.24	7 / 4	2026-03-17
0.2.23	7 / 4	2026-02-17
0.2.22	7 / 4	2025-12-16
0.2.21	7 / 4	2025-11-18
0.2.20	7 / 4	2025-10-14
0.2.19	7 / 4	2025-09-16
0.2.18	7 / 4	2025-08-19
0.2.17	7 / 4	2025-07-15
0.2.16	7 / 4	2025-06-17
0.2.15	7 / 4	2025-05-20
0.2.14	7 / 4	2025-04-15
0.2.13	7 / 4	2025-03-18
0.2.12	7 / 4	2025-02-18
0.2.11	7 / 4	2025-01-14
0.2.10	7 / 4	2024-12-17
0.2.9	8 / 4	2024-11-19
0.2.8	9 / 4	2024-10-18
0.2.7	9 / 4	2024-10-15
0.2.6	9 / 4	2024-09-17
0.2.5	9 / 4	2024-08-27
0.2.4	9 / 4	2024-08-20
0.2.3	9 / 4	2024-07-16
0.2.2	9 / 4	2024-06-26
0.2.1	9 / 4	2024-06-19
0.2.0	9 / 4	2024-06-18
0.1.4	8 / 4	2024-05-14
0.1.3	8 / 4	2024-04-16
0.1.2	8 / 4	2024-03-27
0.1.1	8 / 4	2024-03-22
0.1.0	8 / 4	2024-03-19
0.0.4	8 / 3	2024-03-01
0.0.3	8 / 3	2024-02-23
0.0.2	8 / 3	2024-02-22
0.0.1	8 / 3	2024-02-20

v0.2.28

1 finding

LOW No provenance attestation provenance

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

v0.2.14

1 finding

LOW No provenance attestation provenance

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

v0.2.13

1 finding

LOW No provenance attestation provenance

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

v0.2.12

1 finding

LOW No provenance attestation provenance

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

v0.2.11

1 finding

LOW No provenance attestation provenance

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

v0.2.10

1 finding

LOW No provenance attestation provenance

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

v0.2.9

1 finding

LOW No provenance attestation provenance

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

v0.2.8

1 finding

LOW No provenance attestation provenance

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

v0.2.7

1 finding

LOW No provenance attestation provenance

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

v0.2.6

1 finding

LOW No provenance attestation provenance

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

v0.2.5

1 finding

LOW No provenance attestation provenance

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

v0.2.4

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

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

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