@enbox/protocols
Standard reusable DWN protocol definitions for the Enbox ecosystem
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): Consistent across all @enbox/* packages; absence of provenance is not a risk signal for this org. | ai |
Versions (showing 51 of 101)
| Version | Deps | Published |
|---|---|---|
| 0.2.100 | 2 / 7 | |
| 0.2.99 | 2 / 7 | |
| 0.2.98 | 2 / 7 | |
| 0.2.97 | 2 / 7 | |
| 0.2.96 | 2 / 7 | |
| 0.2.95 | 2 / 7 | |
| 0.2.94 | 2 / 7 | |
| 0.2.93 | 2 / 7 | |
| 0.2.92 | 2 / 5 | |
| 0.2.91 | 2 / 5 | |
| 0.2.90 | 2 / 5 | |
| 0.2.89 | 2 / 5 | |
| 0.2.88 | 2 / 5 | |
| 0.2.87 | 2 / 5 | |
| 0.2.85 | 2 / 5 | |
| 0.2.84 | 2 / 5 | |
| 0.2.83 | 2 / 5 | |
| 0.2.82 | 2 / 5 | |
| 0.2.81 | 2 / 5 | |
| 0.2.80 | 2 / 5 | |
| 0.2.79 | 2 / 5 | |
| 0.2.78 | 2 / 5 | |
| 0.2.77 | 2 / 5 | |
| 0.2.76 | 2 / 5 | |
| 0.2.75 | 2 / 5 | |
| 0.2.74 | 2 / 5 | |
| 0.2.73 | 2 / 5 | |
| 0.2.72 | 2 / 5 | |
| 0.2.71 | 2 / 5 | |
| 0.2.70 | 2 / 5 | |
| 0.2.69 | 2 / 5 | |
| 0.2.68 | 2 / 5 | |
| 0.2.67 | 2 / 5 | |
| 0.2.66 | 2 / 5 | |
| 0.2.65 | 2 / 5 | |
| 0.2.64 | 2 / 5 | |
| 0.2.63 | 2 / 5 | |
| 0.2.62 | 2 / 5 | |
| 0.2.61 | 2 / 5 | |
| 0.2.60 | 2 / 5 | |
| 0.2.59 | 2 / 5 | |
| 0.2.58 | 2 / 5 | |
| 0.2.57 | 2 / 5 | |
| 0.2.56 | 2 / 5 | |
| 0.2.55 | 2 / 5 | |
| 0.2.54 | 2 / 5 | |
| 0.2.53 | 2 / 5 | |
| 0.2.52 | 2 / 5 | |
| 0.2.51 | 2 / 5 | |
| 0.2.50 | 2 / 5 | |
| 0.2.49 | 2 / 5 |
v0.2.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.