← Home

@backstage/plugin-events-node

npm Repository Homepage
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:@types/express AI (phantom-deps): TypeScript type package loaded by convention in the Backstage framework; not a security concern for this package. ai
phantom-deps phantom-dep:@backstage/types AI (phantom-deps): Same-org @backstage scoped type package; used at compile time by convention in the Backstage monorepo ecosystem. ai
phantom-deps phantom-dep:@types/content-type AI (phantom-deps): TypeScript type package loaded by convention; not a security concern for this package. ai

Versions (showing 12 of 12)

Version Deps Published
0.4.22 9 / 3
0.4.21 9 / 3
0.4.20 9 / 3
0.4.19 9 / 3
0.4.18 9 / 3
0.4.17 9 / 3
0.4.16 9 / 3
0.4.15 9 / 3
0.4.14 9 / 3
0.4.13 9 / 3
0.4.12 9 / 3
0.4.11 9 / 3

v0.4.22

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v0.4.15

1 finding
LOW No provenance attestation provenance

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

v0.4.14

1 finding
LOW No provenance attestation provenance

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

v0.4.13

1 finding
LOW No provenance attestation provenance

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

v0.4.12

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