← Home

@zwave-js/cc

npm Repository Homepage

zwave-js: Command Classes

23
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
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package @zwave-js/cc cannot be a typosquat of 'pg'; Levenshtein match is spurious. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @zwave-js/cc cannot be a typosquat of 'qs'; Levenshtein match is spurious. ai
phantom-deps phantom-dep:reflect-metadata AI (phantom-deps): reflect-metadata is a known implicit runtime dependency for decorator-based packages; stable false positive. ai
phantom-deps phantom-dep:ansi-colors AI (phantom-deps): Used in config/build tooling context; stable false positive for this package. ai
phantom-deps phantom-dep:@zwave-js/host AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic unreliable for type-only or indirect imports within monorepos. ai

Versions (showing 23 of 23)

Version Deps Published
15.26.0 7 / 13
15.25.3 7 / 13
15.25.2 7 / 13
15.25.1 7 / 13
15.25.0 7 / 13
15.24.3 7 / 13
15.24.2 7 / 13
15.24.0 7 / 13
15.23.5 7 / 13
15.23.3 7 / 13
15.23.1 7 / 13
15.23.0 7 / 13
15.22.5 7 / 13
15.22.1 7 / 13
15.22.0 7 / 12
15.21.1 6 / 12
15.21.0 6 / 12
15.20.1 6 / 12
15.20.0 6 / 12
15.19.0 6 / 12
15.18.0 6 / 12
15.17.0 6 / 12
15.16.0 6 / 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.22.1

1 finding
LOW No provenance attestation provenance

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

v15.22.0

1 finding
LOW No provenance attestation provenance

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

v15.21.1

1 finding
LOW No provenance attestation provenance

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

v15.21.0

1 finding
LOW No provenance attestation provenance

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

v15.20.1

1 finding
LOW No provenance attestation provenance

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

v15.20.0

1 finding
LOW No provenance attestation provenance

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

v15.19.0

1 finding
LOW No provenance attestation provenance

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

v15.18.0

1 finding
LOW No provenance attestation provenance

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

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

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