@enbox/dwn-clients
Client libraries and shared types for communicating with [DWN Servers](../dwn-server).
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present to elevate this. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.4.25 | 3 / 8 | |
| 0.4.24 | 3 / 8 | |
| 0.4.23 | 3 / 8 | |
| 0.4.22 | 3 / 8 | |
| 0.4.21 | 3 / 8 | |
| 0.4.20 | 3 / 8 | |
| 0.4.19 | 3 / 8 | |
| 0.4.18 | 3 / 8 | |
| 0.4.17 | 3 / 8 | |
| 0.4.16 | 3 / 8 | |
| 0.4.15 | 3 / 8 | |
| 0.4.14 | 3 / 8 | |
| 0.4.13 | 3 / 8 | |
| 0.4.12 | 3 / 8 | |
| 0.4.11 | 4 / 9 | |
| 0.4.10 | 4 / 9 | |
| 0.4.9 | 4 / 9 | |
| 0.4.8 | 4 / 9 | |
| 0.4.7 | 4 / 9 | |
| 0.4.6 | 4 / 9 | |
| 0.4.5 | 4 / 9 | |
| 0.4.4 | 4 / 9 | |
| 0.4.3 | 4 / 9 | |
| 0.4.2 | 4 / 9 | |
| 0.4.1 | 4 / 9 | |
| 0.4.0 | 4 / 9 | |
| 0.3.3 | 4 / 9 | |
| 0.3.2 | 4 / 9 | |
| 0.3.1 | 4 / 9 | |
| 0.3.0 | 4 / 9 | |
| 0.2.6 | 4 / 9 | |
| 0.2.5 | 4 / 9 | |
| 0.2.4 | 4 / 9 | |
| 0.2.3 | 4 / 9 | |
| 0.2.2 | 4 / 9 | |
| 0.2.1 | 4 / 9 | |
| 0.2.0 | 4 / 9 | |
| 0.1.0 | 4 / 10 | |
| 0.0.9 | 4 / 10 | |
| 0.0.8 | 4 / 10 | |
| 0.0.7 | 4 / 10 | |
| 0.0.6 | 4 / 10 | |
| 0.0.5 | 4 / 10 | |
| 0.0.4 | 4 / 10 | |
| 0.0.3 | 4 / 10 | |
| 0.0.2 | 4 / 10 |
v0.4.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.