← Home

@backstage/plugin-notifications-node

npm Repository
12
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

patrikofrebenmarcuseide

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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
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
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
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
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

Versions (showing 12 of 12)

Version Deps Published
0.2.26 2 / 4
0.2.25 7 / 4
0.2.24 7 / 4
0.2.23 7 / 4
0.2.22 7 / 4
0.2.21 7 / 4
0.2.20 7 / 4
0.2.19 7 / 4
0.2.18 7 / 4
0.2.17 7 / 4
0.2.16 7 / 4
0.2.15 7 / 4

v0.2.26

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v0.2.23

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

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

1 finding
LOW No provenance attestation provenance

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

v0.2.19

1 finding
LOW No provenance attestation provenance

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

v0.2.18

1 finding
LOW No provenance attestation provenance

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

v0.2.17

1 finding
LOW No provenance attestation provenance

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

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

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.