@safe-global/safe-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 | publisher-changed | AI (provenance): Publisher rotation within official @safe-global scope; no material change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Legitimate maintainer transition on established org-scoped package. | ai | |
| provenance | missing-githead | AI (provenance): Legit publish-env change on official Safe package; no code-behavior risk. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is not a risk on its own for this established package. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 1.37.60 | 1 / 16 | |
| 1.37.59 | 1 / 16 | |
| 1.37.58 | 1 / 16 | |
| 1.37.57 | 1 / 16 | |
| 1.37.56 | 1 / 15 | |
| 1.37.55 | 1 / 15 | |
| 1.37.54 | 1 / 15 | |
| 1.37.53 | 1 / 15 | |
| 1.37.52 | 1 / 15 | |
| 1.37.51 | 1 / 15 | |
| 1.37.50 | 1 / 15 | |
| 1.37.49 | 1 / 15 | |
| 1.37.48 | 1 / 15 | |
| 1.37.47 | 1 / 15 | |
| 1.37.46 | 1 / 15 | |
| 1.37.45 | 1 / 15 | |
| 1.37.44 | 1 / 15 | |
| 1.37.43 | 1 / 15 | |
| 1.37.42 | 1 / 15 | |
| 1.37.41 | 1 / 15 | |
| 1.37.40 | 1 / 15 | |
| 1.37.39 | 1 / 15 | |
| 1.37.38 | 1 / 15 | |
| 1.37.37 | 1 / 15 | |
| 1.37.36 | 1 / 15 | |
| 1.37.35 | 1 / 15 | |
| 1.37.34 | 1 / 15 | |
| 1.37.33 | 1 / 15 | |
| 1.37.32 | 1 / 15 | |
| 1.37.31 | 1 / 15 | |
| 1.37.30 | 1 / 15 | |
| 1.37.29 | 1 / 15 | |
| 1.37.28 | 1 / 15 | |
| 1.37.27 | 1 / 15 | |
| 1.37.26 | 1 / 15 | |
| 1.37.25 | 1 / 15 | |
| 1.37.24 | 1 / 15 | |
| 1.37.23 | 1 / 15 | |
| 1.37.22 | 1 / 15 | |
| 1.37.21 | 1 / 15 | |
| 1.37.20 | 1 / 15 | |
| 1.37.19 | 1 / 15 | |
| 1.37.18 | 1 / 15 | |
| 1.37.17 | 1 / 15 | |
| 1.37.16 | 1 / 15 | |
| 1.37.15 | 1 / 15 | |
| 1.37.14 | 1 / 15 | |
| 1.37.13 | 1 / 15 | |
| 1.37.12 | 1 / 15 | |
| 1.37.11 | 1 / 15 | |
| 1.37.10 | 1 / 15 |
v1.37.60
2 findings[Accepted risk] Package 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.
v1.37.59
2 findings[Accepted risk] Package 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.
v1.37.58
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.
v1.37.53
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (akshay-ap) than the most recent previously approved version (valens-carpentier) on 2026-03-18, but akshay-ap is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.37.52
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (akshay-ap) than the most recent previously approved version (valens-carpentier) on 2026-03-03, but akshay-ap is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.37.45
2 findingsThis version was published by a different npm account than previous versions on 2025-09-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.44
2 findingsThis version was published by a different npm account than previous versions on 2025-09-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.43
2 findingsThis version was published by a different npm account than previous versions on 2025-09-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.42
2 findingsThis version was published by a different npm account than previous versions on 2025-08-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.41
2 findingsThis version was published by a different npm account than previous versions on 2025-08-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.40
2 findingsThis version was published by a different npm account than previous versions on 2025-07-21. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.39
2 findingsThis version was published by a different npm account than previous versions on 2025-07-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.38
2 findingsThis version was published by a different npm account than previous versions on 2025-07-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.37
2 findingsThis version was published by a different npm account than previous versions on 2025-07-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.36
2 findingsThis version was published by a different npm account than previous versions on 2025-06-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.31
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (akshay-ap) than the most recent previously approved version (safeinfra) on 2025-03-21, but akshay-ap is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.37.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.15
2 findings[Accepted risk] Package 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: safeinfra.
v1.37.14
2 findings[Accepted risk] Package 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: safeinfra.
v1.37.13
2 findings[Accepted risk] Package 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: safeinfra.
v1.37.12
2 findings[Accepted risk] Package 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: safeinfra.
v1.37.11
2 findings[Accepted risk] Package 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: safeinfra.
v1.37.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.