← Home

@backstage/plugin-signals-node

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
dependencies unvetted-dep:@backstage/types AI (dependencies): First-party Backstage monorepo package; same org scope, no third-party risk. ai
dependencies unvetted-dep:@backstage/backend-plugin-api AI (dependencies): First-party Backstage monorepo package; same org scope, no third-party risk. ai
dependencies unvetted-dep:@backstage/plugin-events-node AI (dependencies): First-party Backstage monorepo package; same org scope, no third-party risk. ai
phantom-deps phantom-dep:ws AI (phantom-deps): Declared in package.json dependencies; common Backstage pattern where deps are declared but used indirectly or in type contexts. ai
phantom-deps phantom-dep:uuid AI (phantom-deps): Declared in package.json dependencies; common Backstage pattern where deps are declared but used indirectly or in type contexts. ai
phantom-deps phantom-dep:express AI (phantom-deps): Declared in package.json dependencies; common Backstage pattern where deps are declared but used indirectly or in type contexts. ai
phantom-deps phantom-dep:@backstage/config AI (phantom-deps): Same org scope; declared in dependencies; standard Backstage plugin pattern. ai
phantom-deps phantom-dep:@backstage/plugin-auth-node AI (phantom-deps): Same org scope; declared in dependencies; standard Backstage plugin pattern. ai
provenance no-provenance AI (provenance): Established Backstage package with 81.9k weekly downloads; lack of provenance is common and not a risk signal here. ai

Versions (showing 12 of 12)

Version Deps Published
0.2.1 3 / 2
0.2.0 8 / 2
0.1.29 8 / 2
0.1.28 8 / 2
0.1.27 8 / 2
0.1.26 8 / 2
0.1.25 8 / 2
0.1.24 8 / 2
0.1.23 8 / 2
0.1.22 8 / 2
0.1.21 8 / 2
0.1.20 8 / 2

v0.2.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] 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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.29

1 finding
INFO No provenance attestation provenance

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

v0.1.28

1 finding
INFO No provenance attestation provenance

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

v0.1.27

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.26

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.25

1 finding
INFO No provenance attestation provenance

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

v0.1.24

1 finding
INFO No provenance attestation provenance

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

v0.1.23

1 finding
INFO No provenance attestation provenance

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

v0.1.22

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.21

1 finding
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.