@mysten/zklogin
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
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): @mysten/sui replaces @mysten/sui.js in same diff; first-party monorepo package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consistent with normal Mysten Labs team rotation across large monorepo. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is an intentional deprecation stub redirecting to @mysten/sui/zklogin; minimal README and no keywords are expected for this type of shim package. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 0.8.1 | 1 / 4 | |
| 0.8.0 | 1 / 4 | |
| 0.7.30 | 5 / 4 | |
| 0.7.29 | 5 / 4 | |
| 0.7.28 | 5 / 4 | |
| 0.7.27 | 5 / 4 | |
| 0.7.26 | 5 / 4 | |
| 0.7.25 | 5 / 4 | |
| 0.7.24 | 5 / 4 | |
| 0.7.23 | 5 / 4 | |
| 0.7.22 | 5 / 4 | |
| 0.7.21 | 5 / 4 | |
| 0.7.20 | 5 / 4 | |
| 0.7.19 | 5 / 4 | |
| 0.7.18 | 5 / 4 | |
| 0.7.17 | 5 / 4 | |
| 0.7.16 | 5 / 4 | |
| 0.7.15 | 5 / 4 | |
| 0.7.14 | 5 / 4 | |
| 0.7.13 | 5 / 4 | |
| 0.7.12 | 5 / 4 | |
| 0.7.11 | 5 / 4 | |
| 0.7.10 | 5 / 4 | |
| 0.7.9 | 5 / 4 | |
| 0.7.8 | 5 / 4 | |
| 0.7.7 | 5 / 4 | |
| 0.7.6 | 5 / 4 | |
| 0.7.5 | 5 / 4 | |
| 0.7.4 | 5 / 4 | |
| 0.7.3 | 5 / 4 | |
| 0.7.2 | 5 / 4 | |
| 0.7.1 | 5 / 4 | |
| 0.7.0 | 5 / 4 | |
| 0.6.3 | 5 / 4 | |
| 0.6.2 | 5 / 4 | |
| 0.6.1 | 5 / 4 | |
| 0.6.0 | 5 / 4 | |
| 0.5.3 | 5 / 4 | |
| 0.5.2 | 5 / 4 | |
| 0.5.1 | 5 / 4 | |
| 0.5.0 | 5 / 4 | |
| 0.4.3 | 5 / 4 | |
| 0.4.2 | 5 / 4 | |
| 0.4.1 | 5 / 4 | |
| 0.4.0 | 5 / 4 | |
| 0.3.10 | 5 / 5 | |
| 0.3.9 | 5 / 5 | |
| 0.3.8 | 5 / 5 |
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.