@coinflowlabs/react
React Component for Coinflow Withdraw
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with 111 versions; lack of provenance is consistent with its history and common for this ecosystem segment. | ai | |
| phantom-deps | phantom-dep:bn.js | AI (phantom-deps): bn.js is a declared runtime dep used transitively by Solana/crypto libs; phantom-dep false positive for this package. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 5.20.0 | 4 / 3 | |
| 5.19.0 | 4 / 3 | |
| 5.18.0 | 4 / 3 | |
| 5.17.0 | 4 / 3 | |
| 5.16.0 | 4 / 3 | |
| 5.15.0 | 4 / 3 | |
| 5.14.0 | 4 / 3 | |
| 5.13.0 | 4 / 3 | |
| 5.12.0 | 4 / 3 | |
| 5.11.0 | 4 / 3 | |
| 5.10.0 | 4 / 3 | |
| 5.9.2 | 4 / 3 | |
| 5.9.1 | 4 / 3 | |
| 5.8.1 | 4 / 3 | |
| 5.8.0 | 4 / 3 | |
| 5.7.0 | 4 / 3 | |
| 5.6.0 | 4 / 3 | |
| 5.5.1 | 4 / 4 | |
| 5.5.0 | 4 / 4 | |
| 5.4.4 | 4 / 4 | |
| 5.4.3 | 3 / 4 | |
| 5.4.2 | 3 / 4 | |
| 5.4.1 | 3 / 4 | |
| 5.4.0 | 3 / 4 | |
| 5.3.1 | 3 / 4 | |
| 5.3.0 | 3 / 4 | |
| 5.2.3 | 3 / 4 | |
| 5.2.2 | 3 / 4 | |
| 5.2.1 | 3 / 4 | |
| 5.2.0 | 3 / 4 | |
| 5.1.0 | 3 / 4 | |
| 5.0.9 | 3 / 4 | |
| 5.0.8 | 3 / 4 | |
| 5.0.7 | 3 / 4 | |
| 5.0.6 | 3 / 4 | |
| 5.0.5 | 3 / 4 | |
| 5.0.4 | 3 / 4 | |
| 5.0.3 | 3 / 4 | |
| 5.0.2 | 3 / 4 | |
| 5.0.1 | 3 / 4 | |
| 5.0.0 | 3 / 4 |
v5.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.