@layerzerolabs/layerzero-definitions
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): LayerZero publishes via bot without Sigstore provenance; consistent across 770 approved packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo utility package from established LayerZero org; missing metadata is a style choice, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across LayerZero monorepo packages; not a malice signal for this publisher. | ai |
Versions (showing 48 of 150)
| Version | Deps | Published |
|---|---|---|
| 0.0.66 | 3 / 4 | |
| 0.0.65 | 3 / 4 | |
| 0.0.64 | 3 / 4 | |
| 0.0.63 | 3 / 4 | |
| 0.0.62 | 3 / 4 | |
| 0.0.61 | 3 / 4 | |
| 0.0.60 | 3 / 4 | |
| 0.0.59 | 3 / 4 | |
| 0.0.58 | 3 / 4 | |
| 0.0.57 | 3 / 4 | |
| 0.0.56 | 3 / 4 | |
| 0.0.54 | 3 / 4 | |
| 0.0.53 | 3 / 4 | |
| 0.0.52 | 3 / 4 | |
| 0.0.51 | 3 / 4 | |
| 0.0.50 | 3 / 4 | |
| 0.0.49 | 3 / 4 | |
| 0.0.48 | 3 / 4 | |
| 0.0.47 | 3 / 4 | |
| 0.0.46 | 3 / 4 | |
| 0.0.45 | 4 / 4 | |
| 0.0.44 | 4 / 4 | |
| 0.0.43 | 4 / 4 | |
| 0.0.42 | 4 / 4 | |
| 0.0.41 | 4 / 4 | |
| 0.0.40 | 4 / 4 | |
| 0.0.39 | 4 / 4 | |
| 0.0.35 | 4 / 4 | |
| 0.0.34 | 4 / 4 | |
| 0.0.33 | 4 / 4 | |
| 0.0.32 | 4 / 4 | |
| 0.0.31 | 4 / 4 | |
| 0.0.30 | 3 / 4 | |
| 0.0.29 | 3 / 4 | |
| 0.0.26 | 3 / 5 | |
| 0.0.25 | 3 / 5 | |
| 0.0.24 | 3 / 5 | |
| 0.0.23 | 3 / 5 | |
| 0.0.22 | 3 / 5 | |
| 0.0.21 | 3 / 6 | |
| 0.0.20 | 3 / 6 | |
| 0.0.19 | 3 / 6 | |
| 0.0.18 | 3 / 6 | |
| 0.0.17 | 3 / 6 | |
| 0.0.16 | 3 / 6 | |
| 0.0.15 | 3 / 6 | |
| 0.0.9 | 3 / 6 | |
| 0.0.8 | 3 / 6 |
v0.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.