@layerzerolabs/common-chain-model
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package from established LayerZero org; sparse metadata is consistent across all their packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across LayerZero monorepo packages; not a malware indicator here. | ai |
Versions (showing 20 of 122)
| Version | Deps | Published |
|---|---|---|
| 0.0.66 | 2 / 4 | |
| 0.0.65 | 2 / 4 | |
| 0.0.64 | 2 / 4 | |
| 0.0.63 | 2 / 4 | |
| 0.0.62 | 2 / 4 | |
| 0.0.61 | 2 / 4 | |
| 0.0.60 | 2 / 4 | |
| 0.0.59 | 2 / 4 | |
| 0.0.58 | 2 / 4 | |
| 0.0.57 | 2 / 4 | |
| 0.0.56 | 2 / 4 | |
| 0.0.54 | 2 / 4 | |
| 0.0.53 | 2 / 4 | |
| 0.0.52 | 2 / 4 | |
| 0.0.51 | 2 / 4 | |
| 0.0.50 | 2 / 4 | |
| 0.0.49 | 2 / 4 | |
| 0.0.48 | 2 / 4 | |
| 0.0.47 | 2 / 4 | |
| 0.0.46 | 2 / 4 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.