← Home

@waku/utils

Different utilities for Waku

11
Versions
MIT OR Apache-2.0
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

royerfranckrichard-ramoswebokoseemenkina

Keywords

wakudecentralizedsecurecommunicationweb3ethereumdappsprivacy

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:chai AI (phantom-deps): chai is a test dependency accidentally listed in dependencies; not a security risk for this package. ai
provenance no-provenance AI (provenance): Established Waku monorepo package; lack of provenance is consistent across all versions. ai

Versions (showing 11 of 11)

Version Deps Published
0.0.27 5 / 8
0.0.26 5 / 8
0.0.25 5 / 8
0.0.24 5 / 8
0.0.23 5 / 8
0.0.22 5 / 8
0.0.21 5 / 8
0.0.20 5 / 8
0.0.19 5 / 8
0.0.18 5 / 8
0.0.17 5 / 8

v0.0.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.0.22

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

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

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

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

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

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.