Skip to content
Back to search

pyth-crosschain

Crosschain Pyth programs and utilities

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/pyth-network/pyth-crosschain with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/pyth-network/pyth-crosschain'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/pyth-network--pyth-crosschain/badge.svg)](/listings/pyth-network--pyth-crosschain)

HTML

<a href="/listings/pyth-network--pyth-crosschain"><img src="/api/listings/pyth-network--pyth-crosschain/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Please install the following tools in order to work in this repository:

- [NVM](https://github.com/nvm-sh/nvm?tab=readme-ov-file#installing-and-updating) to manage your node version, then run `nvm use 22` to ensure you are using node version 22. - Optionally, you can also use [mise](https://mise.jdx.dev/). If you install `mise`, you can run all of your commands like the following: `mise x -- pnpm <SOME_COMMAND>`, which will ensure you are running your commands while using the correct tool versions for this repository. - [Foundry](https://book.getfoundry.sh/getting-started/installation) in order to use `forge` for Ethereum contract development - [Solana CLI](https://solana.com/docs/intro/installation) for working with Solana programs. - After installing, please run `solana keygen new` to generate a local private key. - [Anchor](https://www.anchor-lang.com/docs/installation) for developing Solana programs. - [Pre-commit](https://pre-commit.com/) is used to automatically format and lint the repository. - After installing, please run `pre-commit install` in the root of the repo to configure the checks to run on each git commit. - [Rust](https://www.rust-lang.org/tools/install)

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 162 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Pyth Crosschain
  2. This repository acts as a monorepo for the various components that make up
  3. Pyth protocols.
  4. Within this monorepo you will find the following subprojects:
  5. ## Table of Contents
  6. - [Target Chains](#target-chains)
  7. - [Hermes](#hermes)
  8. - [Fortuna](#fortuna)
  9. - [Pyth Lazer Pusher](#pyth-lazer-pusher)
  10. - [Local Development](#local-development)
  11. - [Setup](#setup)
  12. - [Pull requests](#pull-requests)
  13. - [Releases](#releases)
  14. - [Typescript Monorepo](#typescript-monorepo)
  15. - [Setting up](#setting-up)
  16. - [Common tasks](#common-tasks)
  17. - [Building a new web app, JS / TS library or CLI tool](#building-a-new-web-app-js--ts-library-or-cli-tool)
  18. - [Audit / Feature Status](#audit--feature-status)
  19. ## Target Chains
  20. > [target_chains](./target_chains/)
  21. This directory contains on-chain contracts and SDKs for all of the various
  22. blockchain runtimes that Pyth supports. Each subdirectory corresponds to a
  23. blockchain runtime. Inside each subdirectory, there are subfolders for
  24. contracts and SDKs.
  25. ## Hermes
  26. > [hermes](./apps/hermes/)
  27. Hermes is an off-chain service which constantly observes Pythnet and the
  28. Wormhole network watching for price updates emitted from the Pyth contract. It
  29. exposes all observed attestations via a public API over HTTPS/WSS which can be
  30. consumed by client-side applications that wish to use Pyth pricing data.
  31. The [`price_service/client`](./price_service/client/) directory provides an SDK for interacting with Hermes.
  32. However, most users will interact with the price service via a chain-specific SDK
  33. For a guide on utilising this service in your project, see the chain-specific SDK
  34. and [examples](https://github.com/pyth-network/pyth-examples/tree/main/price_feeds) for your blockchain runtime in the `target_chains` directory.
  35. ## Fortuna
  36. > [fortuna](./apps/fortuna/)
  37. Fortuna is an off-chain service which can be used by [Entropy](https://pyth.network/entropy) providers.
  38. ## Pyth Lazer Pusher
  39. > [pyth-lazer-pusher](./apps/pyth-lazer-pusher/)
  40. Price feed pushers that deliver Pyth Lazer data to external systems. Currently supports pushing to Bulk Trade validators.
  41. ## Local Development
  42. ### Setup
  43. Please install the following tools in order to work in this repository:
  44. - [NVM](https://github.com/nvm-sh/nvm?tab=readme-ov-file#installing-and-updating) to manage your node version, then run `nvm use 22` to ensure you are using node version 22.
  45. - Optionally, you can also use [mise](https://mise.jdx.dev/). If you install `mise`, you can run all of your commands like the following: `mise x -- pnpm <SOME_COMMAND>`, which will ensure you are running your commands while using the correct tool versions for this repository.
  46. - [Foundry](https://book.getfoundry.sh/getting-started/installation) in order to use `forge` for Ethereum contract development
  47. - [Solana CLI](https://solana.com/docs/intro/installation) for working with Solana programs.
  48. - After installing, please run `solana keygen new` to generate a local private key.
  49. - [Anchor](https://www.anchor-lang.com/docs/installation) for developing Solana programs.
  50. - [Pre-commit](https://pre-commit.com/) is used to automatically format and lint the repository.
  51. - After installing, please run `pre-commit install` in the root of the repo to configure the checks to run on each git commit.
  52. - [Rust](https://www.rust-lang.org/tools/install)
  53. ### Pull requests
  54. Use the [Conventional Commits](https://www.conventionalcommits.org) format for your commit messages and PR titles.
  55. In the PR description, please include a summary of the changes and any relevant context. Also, please make sure
  56. to update the package versions following the [Semantic Versioning](https://semver.org/) rules.
  57. See also: [Standards](standards/AGENTS.md)
  58. ### Releases
  59. The repository has several CI workflows that automatically release new versions of the various components when a new Github release is published.
  60. Each component's workflow uses a specific tag format including the component name and version number (e.g., Fortuna uses the tag `fortuna-vX.Y.Z`).
  61. The general process for creating a new release is:
  62. 1. Update the version number of the component in the repo, e.g., in `package.json` or `Cargo.toml` or wherever. Please follow [Semantic Versioning](https://semver.org/) for package versions.
  63. 2. Submit a PR with the changes and merge them in to main.
  64. 3. Create a new release on github. Configure the release to create a new tag when published. Set the tag name and version for the component you wish to release -- see the [Releases](https://github.com/pyth-network/pyth-crosschain/releases) page to identify the relevant tag.
  65. 4. Publish the release. This step will automatically trigger a Github Action to build the package and release it. This step will e.g., publish packages to NPM, or build and push docker images.
  66. - Note that when publishing a public package, you should prune the auto-generated Github release notes to only include changes relevant to the release. Otherwise, the changelog will include commits from unrelated projects in the monorepo since the previous release.
  67. Note that all javascript packages are released together using a tag of the form `pyth-js-v<number>`. (The `number` is arbitrary.)
  68. If you have a javascript package that shouldn't be published, simply add `"private": "true"` to the `package.json` file
  69. and it will be excluded from the publishing workflow. If you are creating a new public javascript package, you should add
  70. the following config option to `package.json`:
  71. ```
  72. "publishConfig": {
  73. "access": "public"
  74. },
  75. ```
  76. ### Typescript Monorepo
  77. All of the typescript / javascript packages in this repository are part of a
  78. [turborepo](https://turbo.build/repo/docs) monorepo.
  79. #### Setting up
  80. If you use nix and direnv, just cd to the project directory and `direnv allow`.
  81. If you use nix but not direnv, just cd to the project directory and enter a nix
  82. development shell with `nix develop`.
  83. If you don't use nix at all, then install the required system packages:
  84. - [Node.js](https://nodejs.org/en) -- match the version to `.nvmrc`; you can use
  85. [nvm](https://github.com/nvm-sh/nvm) to manage your Node.js version.
  86. - [pnpm](https://pnpm.io/) -- match the version to the version specified in
  87. `package.json`; you can experiment with
  88. [corepack](https://nodejs.org/api/corepack.html) to manage your pnpm version
  89. for you.
  90. #### Common tasks
  91. The following tasks are the most common ways to interact with the monorepo.
  92. Thanks to [turborepo](https://turbo.build/repo/docs), these tasks will
  93. coordinate building any needed dependencies, and task execution will be cached
  94. and will only re-run as necessary. For any of the following tasks, you can pass
  95. [any valid `turbo run` option](https://turbo.build/repo/docs/reference/run)
  96. after `--`, for instance you could run `pnpm test -- --concurrency 2`.
  97. - `pnpm turbo test`: Run all unit tests, integration tests, linting, and format
  98. checks, as well as whatever other code checks any packages support.
  99. - `pnpm turbo fix`: Run auto fixes, including reformatting code and auto-fixing
  100. lint rules where possible.
  101. - `pnpm turbo start:dev`: Start all development servers in parallel.
  102. - `pnpm turbo start:prod`: Run production builds and start production mode
  103. servers in parallel.
  104. #### Building a new web app, JS / TS library or CLI tool
  105. To quickly get started, from the root of this repo, you can run the following:
  106. 1. `pnpm create-pyth-package`
  107. 2. Answer the prompts
  108. 3. Once the script is done, you will have your new webb app, library or CLI tool bootstrapped with all the current best practices.
  109. If you'd like to read more about the best practices, checkout this best practices doc:
  110. [🔗 Creating a new JavaScript / TypeScript Package](./standards/typescript/packages.md)
  111. ## Audit / Feature Status
  112. ⚠ **This software is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
  113. implied. See the License for the specific language governing permissions and limitations under the License.** Or plainly
  114. spoken - this is a very complex piece of software which targets a bleeding-edge, experimental smart contract runtime.
  115. Mistakes happen, and no matter how hard you try and whether you pay someone to audit it, it may eat your tokens, set
  116. your printer on fire or startle your cat. Cryptocurrencies are a high-risk investment, no matter how fancy.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.