← Home

@waku/core

npm Repository Homepage

TypeScript implementation of the Waku v2 protocol

9
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

royerfranckweboko

Keywords

wakudecentralisedcommunicationweb3ethereumdapps

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): @waku/core is the canonical Waku protocol package, not a typosquat of cors; name similarity is coincidental. ai
phantom-deps phantom-dep:debug AI (phantom-deps): debug is a declared runtime dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@waku/enr AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:@libp2p/ping AI (phantom-deps): Declared runtime dep used via libp2p integration; phantom-dep heuristic false positive. ai

Versions (showing 9 of 9)

Version Deps Published
0.0.40 12 / 21
0.0.37 12 / 21
0.0.35 11 / 21
0.0.34 11 / 21
0.0.33 11 / 19
0.0.32 12 / 18
0.0.31 12 / 18
0.0.30 12 / 18
0.0.29 12 / 18

v0.0.35

1 finding
LOW No provenance attestation provenance

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

v0.0.34

1 finding
LOW No provenance attestation provenance

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

v0.0.33

1 finding
LOW No provenance attestation provenance

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

v0.0.32

1 finding
LOW No provenance attestation provenance

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

v0.0.31

1 finding
LOW No provenance attestation provenance

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

v0.0.30

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.

v0.0.29

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.