@safe-global/safe-modules-deployments
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 | missing-githead | AI (provenance): Build-env metadata change on established Safe package; no behavioral risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Maintainer add within Safe org; benign for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.0.8 | 0 / 13 | |
| 3.0.7 | 0 / 13 | |
| 3.0.6 | 0 / 13 | |
| 3.0.4 | 0 / 13 | |
| 3.0.3 | 0 / 13 | |
| 3.0.2 | 0 / 13 | |
| 2.2.24 | 0 / 10 | |
| 2.2.23 | 0 / 10 | |
| 2.2.22 | 0 / 8 | |
| 2.2.21 | 0 / 8 | |
| 2.2.20 | 0 / 8 | |
| 2.2.19 | 0 / 8 |
v3.0.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zalens02.
v3.0.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zalens02.
v3.0.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zalens02.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.