@coinbase/cdp-react
This package contains ready-made, customizable React UI components that wrap the CDP frontend 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Size growth consistent with adding multiple UI components and their dependencies; no malicious payload indicators. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Rapidly growing Coinbase UI component library; new files reflect legitimate component additions. | ai | |
| provenance | publisher-changed | AI (provenance): Coinbase org migrated publishing to GitHub Actions CI/CD; expected for this package going forward. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is the documented version for Coinbase placeholder/namespace reservation packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Intentional namespace placeholder by Coinbase; all bogus-package signals are expected for this use case. | ai | |
| source-diff | obfuscated-file:dist/utils/formatPhoneNumber.js | AI (source-diff): File contains libphonenumber-js phone metadata (country codes, dial prefixes) — expected minified data bundle from declared dependency. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): clsx is a declared runtime dependency and commonly used in React component libraries via CSS class utilities; stable false positive. | ai |
Versions (showing 9 of 109)
| Version | Deps | Published |
|---|---|---|
| 0.0.8 | 3 / 23 | |
| 0.0.7 | 3 / 23 | |
| 0.0.6 | 3 / 23 | |
| 0.0.5 | 3 / 23 | |
| 0.0.4 | 3 / 23 | |
| 0.0.3 | 3 / 23 | |
| 0.0.2 | 3 / 23 | |
| 0.0.1 | 3 / 23 | |
| 0.0.0 | 0 / 0 |
v0.0.8
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.