{"id":19844389,"url":"https://github.com/pyth-network/pyth-crosschain","last_synced_at":"2026-04-16T10:03:24.132Z","repository":{"id":36959092,"uuid":"425803244","full_name":"pyth-network/pyth-crosschain","owner":"pyth-network","description":"Crosschain Pyth programs and utilities","archived":false,"fork":false,"pushed_at":"2025-12-25T08:53:40.000Z","size":471757,"stargazers_count":221,"open_issues_count":91,"forks_count":318,"subscribers_count":23,"default_branch":"main","last_synced_at":"2025-12-26T04:24:41.222Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"https://pyth.network","language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/pyth-network.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":"funding.json","license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":".github/CODEOWNERS","security":"SECURITY.md","support":null,"governance":"governance/pyth_staking_sdk/.gitignore","roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null},"funding":{}},"created_at":"2021-11-08T11:03:15.000Z","updated_at":"2025-12-25T11:52:37.000Z","dependencies_parsed_at":"2024-06-20T12:13:51.825Z","dependency_job_id":"fb7e96cc-36f1-45a5-a088-9c357df336bb","html_url":"https://github.com/pyth-network/pyth-crosschain","commit_stats":{"total_commits":3674,"total_committers":86,"mean_commits":42.72093023255814,"dds":0.8456722917800762,"last_synced_commit":"2faddf96bc22e1aedc1f72f929cb1a64b520db6a"},"previous_names":[],"tags_count":969,"template":false,"template_full_name":null,"purl":"pkg:github/pyth-network/pyth-crosschain","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/pyth-network%2Fpyth-crosschain","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/pyth-network%2Fpyth-crosschain/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/pyth-network%2Fpyth-crosschain/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/pyth-network%2Fpyth-crosschain/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/pyth-network","download_url":"https://codeload.github.com/pyth-network/pyth-crosschain/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/pyth-network%2Fpyth-crosschain/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28337870,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-12T06:09:07.588Z","status":"ssl_error","status_checked_at":"2026-01-12T06:05:18.301Z","response_time":98,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-12T13:03:58.396Z","updated_at":"2026-04-16T10:03:24.118Z","avatar_url":"https://github.com/pyth-network.png","language":"TypeScript","funding_links":[],"categories":["**6\\. Detailed Data Tables of Financial Projects**","Solana Agent Infrastructure"],"sub_categories":["**Table 3: Emerging Chains \u0026 Infrastructure**","Benchmark Reality Check (real-world tool use)"],"readme":"# Pyth Crosschain\n\nThis repository acts as a monorepo for the various components that make up\nPyth protocols.\n\nWithin this monorepo you will find the following subprojects:\n\n## Table of Contents\n\n- [Target Chains](#target-chains)\n- [Hermes](#hermes)\n- [Fortuna](#fortuna)\n- [Pyth Lazer Pusher](#pyth-lazer-pusher)\n- [Local Development](#local-development)\n  - [Setup](#setup)\n  - [Pull requests](#pull-requests)\n  - [Releases](#releases)\n  - [Typescript Monorepo](#typescript-monorepo)\n    - [Setting up](#setting-up)\n    - [Common tasks](#common-tasks)\n    - [Building a new web app, JS / TS library or CLI tool](#building-a-new-web-app-js--ts-library-or-cli-tool)\n- [Audit / Feature Status](#audit--feature-status)\n\n## Target Chains\n\n\u003e [target_chains](./target_chains/)\n\nThis directory contains on-chain contracts and SDKs for all of the various\nblockchain runtimes that Pyth supports. Each subdirectory corresponds to a\nblockchain runtime. Inside each subdirectory, there are subfolders for\ncontracts and SDKs.\n\n## Hermes\n\n\u003e [hermes](./apps/hermes/)\n\nHermes is an off-chain service which constantly observes Pythnet and the\nWormhole network watching for price updates emitted from the Pyth contract. It\nexposes all observed attestations via a public API over HTTPS/WSS which can be\nconsumed by client-side applications that wish to use Pyth pricing data.\n\nThe [`price_service/client`](./price_service/client/) directory provides an SDK for interacting with Hermes.\nHowever, most users will interact with the price service via a chain-specific SDK\n\nFor a guide on utilising this service in your project, see the chain-specific SDK\nand [examples](https://github.com/pyth-network/pyth-examples/tree/main/price_feeds) for your blockchain runtime in the `target_chains` directory.\n\n## Fortuna\n\n\u003e [fortuna](./apps/fortuna/)\n\nFortuna is an off-chain service which can be used by [Entropy](https://pyth.network/entropy) providers.\n\n## Pyth Lazer Pusher\n\n\u003e [pyth-lazer-pusher](./apps/pyth-lazer-pusher/)\n\nPrice feed pushers that deliver Pyth Lazer data to external systems. Currently supports pushing to Bulk Trade validators.\n\n## Local Development\n\n### Setup\n\nPlease install the following tools in order to work in this repository:\n\n- [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.\n  - 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 \u003cSOME_COMMAND\u003e`, which will ensure you are running your commands while using the correct tool versions for this repository.\n- [Foundry](https://book.getfoundry.sh/getting-started/installation) in order to use `forge` for Ethereum contract development\n- [Solana CLI](https://solana.com/docs/intro/installation) for working with Solana programs.\n  - After installing, please run `solana keygen new` to generate a local private key.\n- [Anchor](https://www.anchor-lang.com/docs/installation) for developing Solana programs.\n- [Pre-commit](https://pre-commit.com/) is used to automatically format and lint the repository.\n  - After installing, please run `pre-commit install` in the root of the repo to configure the checks to run on each git commit.\n- [Rust](https://www.rust-lang.org/tools/install)\n\n### Pull requests\n\nUse the [Conventional Commits](https://www.conventionalcommits.org) format for your commit messages and PR titles.\nIn the PR description, please include a summary of the changes and any relevant context. Also, please make sure\nto update the package versions following the [Semantic Versioning](https://semver.org/) rules.\n\nSee also: [Code guidelines](doc/code-guidelines.md)\n\n### Releases\n\nThe repository has several CI workflows that automatically release new versions of the various components when a new Github release is published.\nEach 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`).\nThe general process for creating a new release is:\n\n1. 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.\n2. Submit a PR with the changes and merge them in to main.\n3. 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.\n4. 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.\n   - 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.\n\nNote that all javascript packages are released together using a tag of the form `pyth-js-v\u003cnumber\u003e`. (The `number` is arbitrary.)\nIf you have a javascript package that shouldn't be published, simply add `\"private\": \"true\"` to the `package.json` file\nand it will be excluded from the publishing workflow. If you are creating a new public javascript package, you should add\nthe following config option to `package.json`:\n\n```\n  \"publishConfig\": {\n    \"access\": \"public\"\n  },\n```\n\n### Typescript Monorepo\n\nAll of the typescript / javascript packages in this repository are part of a\n[turborepo](https://turbo.build/repo/docs) monorepo.\n\n#### Setting up\n\nIf you use nix and direnv, just cd to the project directory and `direnv allow`.\n\nIf you use nix but not direnv, just cd to the project directory and enter a nix\ndevelopment shell with `nix develop`.\n\nIf you don't use nix at all, then install the required system packages:\n\n- [Node.js](https://nodejs.org/en) -- match the version to `.nvmrc`; you can use\n  [nvm](https://github.com/nvm-sh/nvm) to manage your Node.js version.\n- [pnpm](https://pnpm.io/) -- match the version to the version specified in\n  `package.json`; you can experiment with\n  [corepack](https://nodejs.org/api/corepack.html) to manage your pnpm version\n  for you.\n\n#### Common tasks\n\nThe following tasks are the most common ways to interact with the monorepo.\nThanks to [turborepo](https://turbo.build/repo/docs), these tasks will\ncoordinate building any needed dependencies, and task execution will be cached\nand will only re-run as necessary. For any of the following tasks, you can pass\n[any valid `turbo run` option](https://turbo.build/repo/docs/reference/run)\nafter `--`, for instance you could run `pnpm test -- --concurrency 2`.\n\n- `pnpm turbo test`: Run all unit tests, integration tests, linting, and format\n  checks, as well as whatever other code checks any packages support.\n- `pnpm turbo fix`: Run auto fixes, including reformatting code and auto-fixing\n  lint rules where possible.\n- `pnpm turbo start:dev`: Start all development servers in parallel.\n- `pnpm turbo start:prod`: Run production builds and start production mode\n  servers in parallel.\n\n#### Building a new web app, JS / TS library or CLI tool\n\nTo quickly get started, from the root of this repo, you can run the following:\n\n1. `pnpm create-pyth-package`\n2. Answer the prompts\n3. Once the script is done, you will have your new webb app, library or CLI tool bootstrapped with all the current best practices.\n\nIf you'd like to read more about the best practices, checkout this best practices doc:\n[🔗 Creating a new JavaScript / TypeScript Package](./doc/js-code-guidelines.md)\n\n## Audit / Feature Status\n\n⚠ **This software is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\nimplied. See the License for the specific language governing permissions and limitations under the License.** Or plainly\nspoken - this is a very complex piece of software which targets a bleeding-edge, experimental smart contract runtime.\nMistakes happen, and no matter how hard you try and whether you pay someone to audit it, it may eat your tokens, set\nyour printer on fire or startle your cat. Cryptocurrencies are a high-risk investment, no matter how fancy.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fpyth-network%2Fpyth-crosschain","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fpyth-network%2Fpyth-crosschain","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fpyth-network%2Fpyth-crosschain/lists"}