← Home

@zwave-js/shared

npm Repository Homepage
24
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): zwave-js monorepo uses GitHub Actions for automated publishing; alcalzone→GH Actions is expected CI migration. ai
publish-pattern dormant-publish AI (publish-pattern): Sub-package publish cadence varies; dormancy reflects monorepo release patterns, not account takeover. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a declared runtime dep used implicitly by TypeScript output; stable false positive for this package. ai

Versions (showing 24 of 24)

Version Deps Published
15.26.0 3 / 9
15.25.2 3 / 9
15.24.2 3 / 9
15.24.0 3 / 9
15.23.0 3 / 9
15.22.1 3 / 9
15.22.0 3 / 9
15.21.0 2 / 9
15.20.0 2 / 9
15.19.0 2 / 9
15.18.0 2 / 9
15.17.0 2 / 9
15.16.0 2 / 9
15.15.1 2 / 9
15.13.0 2 / 9
15.11.0 2 / 9
15.9.0 2 / 9
15.7.0 2 / 9
15.4.0 2 / 9
15.3.0 2 / 9
15.2.1 2 / 9
15.1.2 2 / 9
15.0.4 2 / 9
15.0.0 2 / 9

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