@bnb-chain/canonical-bridge-widget
canonical bridge widget
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@bnb-chain/icons | AI (phantom-deps): Same-org dep in a monorepo widget; phantom detection is a false positive here. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a declared runtime dep; phantom heuristic fires on config-only references in bundled output. | ai | |
| phantom-deps | phantom-dep:react-virtuoso | AI (phantom-deps): Declared runtime dep; phantom heuristic is a false positive for this bundled widget package. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 0.10.4 | 5 / 34 | |
| 0.9.0 | 1 / 39 | |
| 0.8.0 | 1 / 39 | |
| 0.7.1 | 0 / 39 | |
| 0.7.0 | 0 / 39 | |
| 0.6.1 | 0 / 39 | |
| 0.5.19 | 0 / 39 | |
| 0.5.18 | 0 / 39 | |
| 0.5.17 | 0 / 39 | |
| 0.5.16 | 0 / 39 | |
| 0.5.15 | 0 / 39 | |
| 0.5.14 | 0 / 39 | |
| 0.5.12 | 0 / 39 | |
| 0.5.11 | 0 / 39 | |
| 0.5.10 | 0 / 39 | |
| 0.5.9 | 0 / 39 | |
| 0.5.8 | 0 / 39 | |
| 0.5.7 | 0 / 39 | |
| 0.5.6 | 0 / 39 | |
| 0.5.5 | 0 / 39 | |
| 0.5.4 | 0 / 39 | |
| 0.5.2 | 4 / 35 | |
| 0.5.1 | 4 / 35 | |
| 0.5.0 | 4 / 35 | |
| 0.4.1 | 1 / 35 | |
| 0.4.0 | 1 / 35 | |
| 0.3.3 | 1 / 35 | |
| 0.3.2 | 1 / 35 | |
| 0.3.1 | 1 / 35 | |
| 0.3.0 | 1 / 35 | |
| 0.2.0 | 1 / 35 | |
| 0.1.2 | 0 / 34 | |
| 0.1.1 | 0 / 34 | |
| 0.0.7 | 0 / 35 | |
| 0.0.6 | 0 / 35 | |
| 0.0.5 | 0 / 35 | |
| 0.0.4 | 0 / 35 | |
| 0.0.3 | 0 / 35 |
v0.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.