@bnb-chain/canonical-bridge-sdk
canonical bridge 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@layerzerolabs/oft-v2-solana-sdk | AI (dependencies): LayerZero official SDK; legitimate dependency for Solana bridge integration in this package. | ai | |
| dependencies | unvetted-dep:@metaplex-foundation/umi-signer-wallet-adapters | AI (dependencies): Metaplex Foundation official package; standard Solana wallet adapter dependency. | ai | |
| provenance | no-provenance | AI (provenance): Established BNB Chain org package; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 0.7.3 | 9 / 14 | |
| 0.7.0 | 9 / 14 | |
| 0.6.0 | 0 / 15 | |
| 0.5.0 | 0 / 12 | |
| 0.4.7 | 0 / 14 | |
| 0.4.6 | 0 / 14 | |
| 0.4.5 | 0 / 14 | |
| 0.4.4 | 0 / 14 | |
| 0.4.3 | 0 / 14 | |
| 0.4.2 | 0 / 11 | |
| 0.4.1 | 0 / 11 | |
| 0.4.0 | 0 / 11 | |
| 0.3.3 | 0 / 11 | |
| 0.3.2 | 0 / 11 | |
| 0.3.1 | 0 / 11 | |
| 0.3.0 | 0 / 11 | |
| 0.2.0 | 0 / 11 | |
| 0.1.2 | 0 / 14 | |
| 0.1.1 | 0 / 14 | |
| 0.0.18 | 0 / 14 | |
| 0.0.17 | 0 / 14 | |
| 0.0.16 | 0 / 14 | |
| 0.0.15 | 0 / 14 | |
| 0.0.14 | 2 / 12 | |
| 0.0.13 | 2 / 12 | |
| 0.0.12 | 2 / 12 | |
| 0.0.10 | 2 / 12 | |
| 0.0.9 | 2 / 12 | |
| 0.0.8 | 2 / 12 | |
| 0.0.7 | 2 / 12 | |
| 0.0.6 | 2 / 12 | |
| 0.0.5 | 2 / 12 | |
| 0.0.4 | 2 / 12 | |
| 0.0.3 | 2 / 12 |
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.