@layerzerolabs/oft-v2-solana-sdk
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): Established LayerZero SDK package; sparse metadata is typical for org-internal SDKs, not spam. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Known LayerZero org package; missing description is a style choice, not a malware indicator. | ai | |
| phantom-deps | phantom-dep:bn.js | AI (phantom-deps): bn.js is a transitive Solana/web3 dep; phantom-dep heuristic fires on indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv used in test/config scripts; phantom-dep heuristic false positive for this SDK. | ai | |
| phantom-deps | phantom-dep:@metaplex-foundation/beet | AI (phantom-deps): Metaplex beet used in generated Solana code; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@layerzerolabs/lz-foundation | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@layerzerolabs/lz-v2-utilities | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@metaplex-foundation/beet-solana | AI (phantom-deps): Metaplex beet-solana used in generated Solana code; phantom-dep heuristic false positive. | ai |
Versions (showing 67 of 167)
| Version | Deps | Published |
|---|---|---|
| 3.0.68 | 13 / 32 | |
| 3.0.67 | 13 / 32 | |
| 3.0.66 | 13 / 32 | |
| 3.0.65 | 13 / 32 | |
| 3.0.64 | 13 / 32 | |
| 3.0.63 | 13 / 32 | |
| 3.0.62 | 13 / 32 | |
| 3.0.61 | 13 / 32 | |
| 3.0.60 | 13 / 32 | |
| 3.0.59 | 13 / 32 | |
| 3.0.58 | 13 / 32 | |
| 3.0.57 | 13 / 32 | |
| 3.0.56 | 13 / 32 | |
| 3.0.54 | 13 / 32 | |
| 3.0.53 | 13 / 29 | |
| 3.0.52 | 13 / 29 | |
| 3.0.51 | 13 / 29 | |
| 3.0.50 | 13 / 29 | |
| 3.0.49 | 13 / 29 | |
| 3.0.48 | 13 / 29 | |
| 3.0.47 | 13 / 28 | |
| 3.0.46 | 13 / 28 | |
| 3.0.45 | 13 / 28 | |
| 3.0.44 | 13 / 28 | |
| 3.0.43 | 13 / 28 | |
| 3.0.42 | 13 / 28 | |
| 3.0.41 | 13 / 28 | |
| 3.0.40 | 13 / 28 | |
| 3.0.39 | 13 / 28 | |
| 3.0.38 | 13 / 28 | |
| 3.0.37 | 13 / 28 | |
| 3.0.36 | 13 / 28 | |
| 3.0.35 | 13 / 28 | |
| 3.0.34 | 13 / 28 | |
| 3.0.33 | 13 / 28 | |
| 3.0.32 | 13 / 28 | |
| 3.0.31 | 13 / 28 | |
| 3.0.30 | 13 / 28 | |
| 3.0.29 | 13 / 28 | |
| 3.0.28 | 13 / 28 | |
| 3.0.27 | 13 / 28 | |
| 3.0.26 | 13 / 28 | |
| 3.0.25 | 13 / 28 | |
| 3.0.24 | 13 / 28 | |
| 3.0.23 | 13 / 28 | |
| 3.0.22 | 13 / 28 | |
| 3.0.21 | 13 / 28 | |
| 3.0.20 | 13 / 28 | |
| 3.0.19 | 13 / 28 | |
| 3.0.18 | 13 / 28 | |
| 3.0.17 | 13 / 28 | |
| 3.0.16 | 13 / 28 | |
| 3.0.15 | 13 / 28 | |
| 3.0.14 | 13 / 28 | |
| 3.0.12 | 13 / 28 | |
| 3.0.11 | 13 / 28 | |
| 3.0.10 | 13 / 28 | |
| 3.0.9 | 13 / 28 | |
| 3.0.8 | 13 / 28 | |
| 3.0.7 | 13 / 28 | |
| 3.0.6 | 13 / 28 | |
| 3.0.5 | 13 / 28 | |
| 3.0.4 | 13 / 28 | |
| 3.0.3 | 13 / 28 | |
| 3.0.2 | 12 / 28 | |
| 3.0.1 | 12 / 28 | |
| 3.0.0 | 12 / 28 |
v3.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.42
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.