@layerzerolabs/lz-definitions
LayerZero Utility
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established LayerZero org package with clean history; missing gitHead likely reflects a CI/CD pipeline change, not a supply-chain compromise. | ai |
Versions (showing 100 of 174)
| Version | Deps | Published |
|---|---|---|
| 3.1.6 | 1 / 3 | |
| 3.1.5 | 1 / 3 | |
| 3.1.4 | 1 / 3 | |
| 3.1.3 | 1 / 3 | |
| 3.1.2 | 1 / 3 | |
| 3.1.1 | 1 / 3 | |
| 3.1.0 | 1 / 3 | |
| 3.0.168 | 1 / 8 | |
| 3.0.167 | 1 / 8 | |
| 3.0.166 | 1 / 8 | |
| 3.0.165 | 1 / 8 | |
| 3.0.164 | 1 / 8 | |
| 3.0.163 | 1 / 8 | |
| 3.0.162 | 1 / 8 | |
| 3.0.161 | 1 / 8 | |
| 3.0.160 | 1 / 8 | |
| 3.0.159 | 1 / 8 | |
| 3.0.158 | 1 / 8 | |
| 3.0.157 | 1 / 8 | |
| 3.0.156 | 1 / 8 | |
| 3.0.155 | 1 / 8 | |
| 3.0.154 | 1 / 8 | |
| 3.0.153 | 1 / 8 | |
| 3.0.152 | 1 / 8 | |
| 3.0.151 | 1 / 8 | |
| 3.0.150 | 1 / 8 | |
| 3.0.149 | 1 / 8 | |
| 3.0.148 | 1 / 8 | |
| 3.0.147 | 1 / 8 | |
| 3.0.146 | 1 / 8 | |
| 3.0.145 | 1 / 8 | |
| 3.0.144 | 1 / 8 | |
| 3.0.143 | 1 / 8 | |
| 3.0.142 | 1 / 8 | |
| 3.0.141 | 1 / 8 | |
| 3.0.140 | 1 / 8 | |
| 3.0.139 | 1 / 8 | |
| 3.0.138 | 1 / 8 | |
| 3.0.137 | 1 / 8 | |
| 3.0.136 | 1 / 8 | |
| 3.0.135 | 1 / 8 | |
| 3.0.134 | 1 / 8 | |
| 3.0.133 | 1 / 8 | |
| 3.0.132 | 1 / 8 | |
| 3.0.131 | 1 / 8 | |
| 3.0.130 | 1 / 8 | |
| 3.0.129 | 1 / 8 | |
| 3.0.128 | 1 / 8 | |
| 3.0.127 | 1 / 8 | |
| 3.0.126 | 1 / 8 | |
| 3.0.125 | 1 / 8 | |
| 3.0.124 | 1 / 8 | |
| 3.0.123 | 1 / 8 | |
| 3.0.122 | 1 / 8 | |
| 3.0.121 | 1 / 8 | |
| 3.0.120 | 1 / 8 | |
| 3.0.119 | 1 / 8 | |
| 3.0.118 | 1 / 8 | |
| 3.0.117 | 1 / 8 | |
| 3.0.116 | 1 / 8 | |
| 3.0.115 | 1 / 8 | |
| 3.0.114 | 1 / 8 | |
| 3.0.113 | 1 / 8 | |
| 3.0.112 | 1 / 8 | |
| 3.0.111 | 1 / 8 | |
| 3.0.110 | 1 / 8 | |
| 3.0.109 | 1 / 8 | |
| 3.0.108 | 1 / 8 | |
| 3.0.107 | 1 / 8 | |
| 3.0.106 | 1 / 8 | |
| 3.0.105 | 1 / 8 | |
| 3.0.104 | 1 / 8 | |
| 3.0.103 | 1 / 8 | |
| 3.0.102 | 1 / 8 | |
| 3.0.101 | 1 / 8 | |
| 3.0.100 | 1 / 8 | |
| 3.0.99 | 1 / 8 | |
| 3.0.98 | 1 / 8 | |
| 3.0.97 | 1 / 8 | |
| 3.0.96 | 1 / 8 | |
| 3.0.95 | 1 / 8 | |
| 3.0.94 | 1 / 8 | |
| 3.0.93 | 1 / 8 | |
| 3.0.92 | 1 / 8 | |
| 3.0.91 | 1 / 9 | |
| 3.0.90 | 1 / 9 | |
| 3.0.89 | 1 / 9 | |
| 3.0.88 | 1 / 9 | |
| 3.0.87 | 1 / 9 | |
| 3.0.86 | 1 / 9 | |
| 3.0.85 | 1 / 9 | |
| 3.0.84 | 1 / 9 | |
| 3.0.83 | 1 / 9 | |
| 3.0.82 | 1 / 9 | |
| 3.0.81 | 1 / 9 | |
| 3.0.80 | 1 / 9 | |
| 3.0.79 | 1 / 9 | |
| 3.0.78 | 1 / 9 | |
| 3.0.77 | 1 / 9 | |
| 3.0.76 | 1 / 9 |
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.