← Home

@zwave-js/host

npm Repository Homepage

zwave-js: Host abstractions

48
Versions
MIT
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): zwave-js monorepo migrated publishing to GitHub Actions CI; consistent with org-level automation, not a takeover. ai
typosquat typosquat.levenshtein:jest AI (typosquat): @zwave-js/host is a scoped monorepo package; Levenshtein match to 'jest' is a false positive. ai
typosquat typosquat.levenshtein:got AI (typosquat): @zwave-js/host is a scoped monorepo package; Levenshtein match to 'got' is a false positive. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for this package. ai
phantom-deps phantom-dep:alcalzone-shared AI (phantom-deps): Referenced in config files per analyzer note; stable false positive for this package. ai

Versions (showing 48 of 48)

Version Deps Published
15.26.0 5 / 5
15.25.3 5 / 5
15.25.2 5 / 5
15.25.1 5 / 5
15.25.0 5 / 5
15.24.3 5 / 5
15.24.2 5 / 5
15.24.0 5 / 5
15.23.5 5 / 5
15.23.3 5 / 5
15.23.1 5 / 5
15.23.0 5 / 5
15.22.5 5 / 5
15.22.1 5 / 5
15.22.0 5 / 5
15.21.0 4 / 5
15.20.1 4 / 5
15.20.0 4 / 5
15.19.0 4 / 5
15.18.0 4 / 5
15.17.0 4 / 5
15.16.0 4 / 5
15.15.3 4 / 5
15.15.2 4 / 5
15.15.1 4 / 5
15.15.0 4 / 5
15.14.0 4 / 5
15.13.0 4 / 5
15.12.0 4 / 5
15.11.0 4 / 5
15.10.0 4 / 5
15.9.0 4 / 5
15.8.0 4 / 5
15.7.0 4 / 5
15.6.0 4 / 5
15.5.0 4 / 5
15.4.0 4 / 5
15.3.2 4 / 5
15.3.0 4 / 5
15.2.1 4 / 5
15.2.0 4 / 5
15.1.2 4 / 5
15.1.1 4 / 5
15.1.0 4 / 5
15.0.6 4 / 5
15.0.4 4 / 5
15.0.1 4 / 5
15.0.0 4 / 5

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

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