@circle-fin/provider-cctp-v2
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:index.cjs | AI (source-diff): Long hex strings are blockchain attestation/message fixtures, not obfuscated payloads; stable pattern for this CCTP SDK. | ai | |
| source-diff | encoded-string-file:index.mjs | AI (source-diff): Same mock attestation hex data duplicated in ESM build; benign for this package. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): Fires on legitimate blockchain RPC/explorer URLs embedded in chain config; stable false positive for this package. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Fires on standard bytes32-to-Solana address hex decoding utility; not a malicious payload. | ai | |
| phantom-deps | phantom-dep:@noble/curves | AI (phantom-deps): Bundled package; dependency may be inlined into the CJS/ESM output rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@coral-xyz/anchor | AI (phantom-deps): Solana SDK dependency likely used via dynamic/conditional imports in bundled output. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.8.3 | 10 / 0 | |
| 1.8.2 | 10 / 0 | |
| 1.8.1 | 10 / 0 | |
| 1.8.0 | 10 / 0 | |
| 1.7.0 | 10 / 0 | |
| 1.6.3 | 10 / 0 | |
| 1.6.2 | 9 / 0 | |
| 1.6.1 | 9 / 0 | |
| 1.6.0 | 9 / 0 | |
| 1.5.0 | 9 / 0 | |
| 1.4.1 | 9 / 0 | |
| 1.4.0 | 10 / 0 | |
| 1.3.1 | 10 / 0 | |
| 1.3.0 | 10 / 0 | |
| 1.2.0 | 10 / 0 | |
| 1.1.0 | 10 / 0 | |
| 1.0.5 | 10 / 0 | |
| 1.0.4 | 10 / 0 | |
| 1.0.3 | 10 / 0 | |
| 1.0.2 | 10 / 0 | |
| 1.0.1 | 10 / 0 | |
| 1.0.0 | 10 / 0 |
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
3 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.