@1delta/dex-registry
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is from the same @1delta org; consistent with package's data-registry purpose. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present for this package. | ai |
Versions (showing 51 of 91)
| Version | Deps | Published |
|---|---|---|
| 0.0.104 | 2 / 9 | |
| 0.0.103 | 2 / 9 | |
| 0.0.102 | 2 / 9 | |
| 0.0.101 | 2 / 9 | |
| 0.0.100 | 2 / 9 | |
| 0.0.99 | 2 / 9 | |
| 0.0.98 | 2 / 9 | |
| 0.0.97 | 2 / 9 | |
| 0.0.96 | 2 / 9 | |
| 0.0.95 | 2 / 9 | |
| 0.0.94 | 2 / 9 | |
| 0.0.93 | 2 / 9 | |
| 0.0.92 | 2 / 9 | |
| 0.0.91 | 2 / 9 | |
| 0.0.90 | 2 / 9 | |
| 0.0.89 | 2 / 9 | |
| 0.0.88 | 2 / 9 | |
| 0.0.87 | 2 / 9 | |
| 0.0.86 | 2 / 9 | |
| 0.0.85 | 2 / 9 | |
| 0.0.84 | 2 / 9 | |
| 0.0.83 | 2 / 9 | |
| 0.0.82 | 2 / 9 | |
| 0.0.81 | 2 / 9 | |
| 0.0.80 | 2 / 9 | |
| 0.0.79 | 2 / 9 | |
| 0.0.78 | 2 / 9 | |
| 0.0.77 | 2 / 9 | |
| 0.0.76 | 2 / 9 | |
| 0.0.75 | 2 / 9 | |
| 0.0.74 | 2 / 9 | |
| 0.0.73 | 2 / 9 | |
| 0.0.72 | 1 / 9 | |
| 0.0.67 | 1 / 9 | |
| 0.0.62 | 1 / 9 | |
| 0.0.59 | 1 / 9 | |
| 0.0.58 | 1 / 9 | |
| 0.0.57 | 1 / 9 | |
| 0.0.56 | 1 / 9 | |
| 0.0.55 | 1 / 9 | |
| 0.0.53 | 1 / 9 | |
| 0.0.50 | 1 / 9 | |
| 0.0.49 | 1 / 9 | |
| 0.0.48 | 0 / 10 | |
| 0.0.47 | 0 / 10 | |
| 0.0.46 | 0 / 10 | |
| 0.0.45 | 0 / 10 | |
| 0.0.44 | 0 / 10 | |
| 0.0.43 | 0 / 10 | |
| 0.0.42 | 0 / 10 | |
| 0.0.41 | 0 / 10 |
v0.0.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.