@layerzerolabs/lz-utilities
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Utility library in monorepo context; missing description is stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Provenance adoption is sparse across npm; not a disqualifier for established publishers. | ai | |
| dependencies | unvetted-dep:@initia/initia.js | AI (dependencies): Multi-chain utility package; @initia/initia.js is a legitimate chain SDK consistent with this package's purpose. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo utility package; missing description/repo/keywords is a consistent pattern across LayerZero's 416 published versions. | ai | |
| phantom-deps | phantom-dep:@ton/core | AI (phantom-deps): Declared as runtime dep in a multi-chain SDK; phantom-dep heuristic fires on indirect usage patterns common in this package. | ai | |
| phantom-deps | phantom-dep:@ethersproject/bytes | AI (phantom-deps): Declared as runtime dep; phantom-dep heuristic fires on indirect usage patterns common in this package. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 3.0.168 | 17 / 12 | |
| 3.0.167 | 17 / 12 | |
| 3.0.164 | 17 / 12 | |
| 3.0.163 | 17 / 12 | |
| 3.0.162 | 17 / 12 | |
| 3.0.160 | 17 / 12 | |
| 3.0.158 | 17 / 12 | |
| 3.0.156 | 17 / 12 | |
| 3.0.154 | 17 / 12 | |
| 3.0.153 | 17 / 12 | |
| 3.0.152 | 17 / 12 | |
| 3.0.151 | 17 / 12 | |
| 3.0.150 | 17 / 12 | |
| 3.0.149 | 17 / 12 | |
| 3.0.148 | 17 / 12 | |
| 3.0.147 | 17 / 12 | |
| 3.0.146 | 17 / 12 | |
| 3.0.145 | 17 / 12 | |
| 3.0.144 | 17 / 12 | |
| 3.0.143 | 17 / 12 | |
| 3.0.142 | 17 / 12 | |
| 3.0.138 | 16 / 12 | |
| 3.0.133 | 16 / 12 | |
| 3.0.131 | 16 / 12 | |
| 3.0.124 | 15 / 12 | |
| 3.0.118 | 15 / 12 | |
| 3.0.111 | 15 / 12 | |
| 3.0.109 | 15 / 12 | |
| 3.0.100 | 15 / 12 | |
| 3.0.99 | 15 / 12 | |
| 3.0.96 | 15 / 12 | |
| 3.0.92 | 15 / 12 | |
| 3.0.90 | 15 / 13 |
v3.0.167
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.164
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.163
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.162
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.160
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.156
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.152
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.151
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.150
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.149
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.148
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.147
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.146
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.145
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.144
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.143
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.142
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.138
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.131
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.