@coinbase/cdp-core
This package contains core business logic for the CDP Frontend SDK. It is intended for non-React applications that use pure Typescript.
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): SDK growth from stub to full implementation; consistent with early-stage package maturation by established publisher. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Coinbase CDP core SDK; large file additions reflect legitimate feature expansion, not injected code. | ai | |
| provenance | missing-githead | AI (provenance): Coinbase-npm has 401 approved packages; occasional gitHead absence reflects CI environment changes, not supply chain compromise. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Explicitly a namespace placeholder by a trusted publisher; low-value signals are expected and intentional. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Intentional placeholder package by Coinbase; 0.0.0 is the declared placeholder version. | ai | |
| phantom-deps | phantom-dep:jose | AI (phantom-deps): jose is a declared runtime dependency in package.json; phantom-dep heuristic misfires here. | ai | |
| dependencies | unvetted-dep:ox | AI (dependencies): ox is a known Ethereum primitive library, co-dependency with viem; stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Coinbase CDP package published via GitHub Actions; provenance absence is common and not a risk signal here. | ai |
Versions (showing 51 of 106)
| Version | Deps | Published |
|---|---|---|
| 0.0.110 | 8 / 4 | |
| 0.0.109 | 8 / 4 | |
| 0.0.108 | 8 / 4 | |
| 0.0.107 | 8 / 4 | |
| 0.0.106 | 8 / 4 | |
| 0.0.105 | 8 / 4 | |
| 0.0.104 | 8 / 4 | |
| 0.0.103 | 8 / 4 | |
| 0.0.102 | 8 / 4 | |
| 0.0.101 | 8 / 4 | |
| 0.0.100 | 8 / 4 | |
| 0.0.99 | 8 / 4 | |
| 0.0.98 | 8 / 4 | |
| 0.0.97 | 8 / 4 | |
| 0.0.96 | 8 / 4 | |
| 0.0.95 | 8 / 4 | |
| 0.0.94 | 8 / 4 | |
| 0.0.93 | 8 / 4 | |
| 0.0.92 | 8 / 4 | |
| 0.0.91 | 8 / 4 | |
| 0.0.90 | 8 / 4 | |
| 0.0.89 | 8 / 4 | |
| 0.0.88 | 8 / 4 | |
| 0.0.87 | 8 / 4 | |
| 0.0.86 | 8 / 4 | |
| 0.0.85 | 8 / 4 | |
| 0.0.84 | 8 / 4 | |
| 0.0.83 | 8 / 4 | |
| 0.0.82 | 8 / 4 | |
| 0.0.81 | 8 / 4 | |
| 0.0.80 | 8 / 4 | |
| 0.0.79 | 8 / 4 | |
| 0.0.78 | 8 / 4 | |
| 0.0.77 | 8 / 4 | |
| 0.0.76 | 8 / 4 | |
| 0.0.75 | 8 / 4 | |
| 0.0.74 | 8 / 4 | |
| 0.0.73 | 8 / 4 | |
| 0.0.72 | 8 / 4 | |
| 0.0.71 | 8 / 4 | |
| 0.0.70 | 8 / 4 | |
| 0.0.69 | 8 / 4 | |
| 0.0.68 | 8 / 4 | |
| 0.0.67 | 8 / 4 | |
| 0.0.66 | 8 / 4 | |
| 0.0.65 | 8 / 4 | |
| 0.0.64 | 8 / 4 | |
| 0.0.63 | 7 / 4 | |
| 0.0.62 | 7 / 4 | |
| 0.0.61 | 7 / 4 | |
| 0.0.60 | 7 / 4 |
v0.0.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.108
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.106
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.