Fix/cosmos native client

[dbrajovic]

Description

Drive-by changes

Related issues

Backward compatibility

Testing

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/cosmos-native-client

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​esbuild/​aix-ppc64@​0.23.1
	@​esbuild/​android-arm64@​0.23.1
	@​esbuild/​darwin-arm64@​0.23.1
	@​esbuild/​darwin-x64@​0.23.1
	@​esbuild/​freebsd-arm64@​0.23.1
	@​esbuild/​freebsd-x64@​0.23.1
	@​esbuild/​linux-arm@​0.23.1
	@​esbuild/​linux-arm64@​0.23.1
	@​esbuild/​linux-ia32@​0.23.1
	@​esbuild/​linux-loong64@​0.23.1
	@​esbuild/​linux-mips64el@​0.23.1
	@​esbuild/​linux-ppc64@​0.23.1
	@​esbuild/​linux-riscv64@​0.23.1
	@​esbuild/​linux-s390x@​0.23.1
	@​esbuild/​linux-x64@​0.23.1
	@​esbuild/​openbsd-arm64@​0.23.1
	@​esbuild/​openbsd-x64@​0.23.1
	@​esbuild/​sunos-x64@​0.23.1
	@​esbuild/​win32-arm64@​0.23.1
	@​esbuild/​win32-ia32@​0.23.1
	@​esbuild/​win32-x64@​0.23.1
	@​esbuild/​netbsd-x64@​0.23.1
	turbo-darwin-arm64@​2.5.3
	turbo-windows-64@​2.5.3
	turbo-darwin-64@​2.5.3
	turbo-linux-64@​2.5.3
	turbo-linux-arm64@​2.5.3
	turbo-windows-arm64@​2.5.3
	@​unrs/​resolver-binding-android-arm-eabi@​1.11.1
	@​unrs/​resolver-binding-android-arm64@​1.11.1
	@​unrs/​resolver-binding-darwin-arm64@​1.11.1
	@​unrs/​resolver-binding-darwin-x64@​1.11.1
See 494 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		@chainlink/[email protected] has a GitHub dependency. Dependency: @zksync/contracts@github:matter-labs/era-contracts@#446d39 Location: Package overview From: ? → npm/@chainlink/[email protected] → npm/@chainlink/[email protected] ℹ Read more on: This package | This alert | What are GitHub dependencies? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Publish the GitHub dependency to npm or a private package repository and consume it from there. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@chainlink/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has Obfuscated code. Confidence: 0.94 Location: Package overview From: yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report