@layerzerolabs/layerzero-v2-ton
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): LayerZero monorepo sub-package; sparse metadata is consistent across all 239 versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across all versions of this monorepo sub-package. | ai | |
| phantom-deps | phantom-dep:crc-32 | AI (phantom-deps): crc-32 is a declared runtime dep; may be used indirectly via build artifacts or config. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 3.0.168 | 1 / 16 | |
| 3.0.167 | 1 / 16 | |
| 3.0.166 | 1 / 16 | |
| 3.0.165 | 1 / 16 | |
| 3.0.164 | 1 / 16 | |
| 3.0.163 | 1 / 16 | |
| 3.0.162 | 1 / 16 | |
| 3.0.161 | 1 / 16 | |
| 3.0.160 | 1 / 16 | |
| 3.0.159 | 1 / 16 | |
| 3.0.158 | 1 / 16 | |
| 3.0.157 | 1 / 16 | |
| 3.0.156 | 1 / 16 | |
| 3.0.155 | 1 / 16 | |
| 3.0.154 | 1 / 16 | |
| 3.0.153 | 1 / 16 | |
| 3.0.152 | 1 / 16 | |
| 3.0.151 | 1 / 16 | |
| 3.0.150 | 1 / 16 | |
| 3.0.149 | 1 / 16 | |
| 3.0.148 | 1 / 16 | |
| 3.0.147 | 1 / 16 | |
| 3.0.146 | 1 / 16 | |
| 3.0.41 | 1 / 16 | |
| 3.0.40 | 1 / 16 | |
| 3.0.39 | 1 / 16 | |
| 3.0.38 | 1 / 16 | |
| 3.0.37 | 1 / 16 | |
| 3.0.36 | 1 / 16 | |
| 3.0.35 | 1 / 16 | |
| 3.0.34 | 1 / 16 | |
| 3.0.33 | 1 / 16 | |
| 3.0.32 | 1 / 16 | |
| 3.0.31 | 1 / 16 | |
| 3.0.30 | 1 / 16 | |
| 3.0.29 | 1 / 16 | |
| 3.0.28 | 1 / 16 | |
| 3.0.27 | 1 / 16 | |
| 3.0.26 | 1 / 16 | |
| 3.0.25 | 1 / 16 | |
| 3.0.24 | 1 / 16 |
v3.0.167
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.166
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.165
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.164
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.163
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.162
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.161
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.159
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.158
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.157
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.156
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.155
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.154
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.153
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.152
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.151
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.150
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.149
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.148
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.147
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.146
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.