@opencxh/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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:history | AI (phantom-deps): Re-exported or indirect dependency in React SDK; stable pattern. | ai | |
| phantom-deps | phantom-dep:i18next | AI (phantom-deps): Re-exported or indirect dependency in React SDK; stable pattern. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Re-exported or indirect dependency in React SDK; stable pattern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.5.0 | 9 / 19 | |
| 3.4.4 | 9 / 19 | |
| 3.3.1 | 11 / 16 | |
| 3.2.2 | 11 / 16 | |
| 3.1.0 | 11 / 16 |
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.