← Home

@zwave-js/core

npm Repository Homepage
35
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

alcalzone

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing is consistent with zwave-js monorepo automation; stable pattern going forward. ai
typosquat typosquat.levenshtein:cors AI (typosquat): @zwave-js/core is a scoped monorepo package unrelated to the 'cors' middleware; Levenshtein match is spurious. ai

Versions (showing 35 of 35)

Version Deps Published
15.26.0 16 / 11
15.25.3 16 / 11
15.25.2 16 / 11
15.25.0 16 / 11
15.24.3 16 / 11
15.24.2 16 / 11
15.24.0 16 / 11
15.23.1 16 / 11
15.23.0 16 / 11
15.22.1 16 / 11
15.22.0 16 / 11
15.21.0 15 / 11
15.20.0 15 / 11
15.19.0 15 / 11
15.18.0 15 / 11
15.17.0 15 / 11
15.16.0 15 / 11
15.15.3 15 / 11
15.15.2 15 / 11
15.15.1 15 / 11
15.15.0 15 / 11
15.13.0 15 / 11
15.11.0 15 / 11
15.10.0 15 / 11
15.9.0 15 / 11
15.7.0 15 / 11
15.6.0 15 / 11
15.4.0 15 / 11
15.3.0 15 / 11
15.2.1 15 / 11
15.1.2 15 / 11
15.1.1 15 / 11
15.0.6 15 / 11
15.0.4 15 / 11
15.0.0 15 / 11

v15.26.0

1 finding
LOW No provenance attestation provenance

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

v15.25.3

1 finding
LOW No provenance attestation provenance

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

v15.25.2

1 finding
LOW No provenance attestation provenance

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

v15.1.2

1 finding
LOW No provenance attestation provenance

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

v15.1.1

1 finding
LOW No provenance attestation provenance

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

v15.0.6

1 finding
LOW No provenance attestation provenance

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

v15.0.4

1 finding
LOW No provenance attestation provenance

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

v15.0.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.