paritytech / polkadot-sdk
The Parity Polkadot Blockchain SDK
- Stars
- 2,811 stars
- Forks
- 1,260 forks
- Language
- Rust
- License
- Not reported
- Created
- Aug 4, 2023
- Last push
- Nov 12, 2026
- Updated
- Nov 12, 2026
Admitted to the Repository Index on Nov 11, 2026: 2,811 stars on 2026-11-11.
Star History
189 days recorded, May 8, 2026 – Nov 12, 2026 (UTC). Net change +97 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour.
Add ?theme=light or ?theme=dark
to the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/paritytech/polkadot-sdk) Badge
[](https://awesomerepos.com/paritytech/polkadot-sdk) Timeline
It gained stars on 77 of the 189 days recorded since May 8, 2026.
Its largest 7 days were May 30, 2026 to Jun 5, 2026: 8 stars.
In the 30 days to Nov 12, 2026 it got 11 stars, 21% fewer than in the 30 days before.
It had 2,714 stars before May 8, 2026 and has 2,811 stars now: 2,189 fewer than 5,000.
- Created on the Repository Host
- +2 stars in one day
- Largest star day recorded: +3 stars
- +3 stars in one day
- Release polkadot-stable2603-8
- Release polkadot-stable2609-1
- Release polkadot-stable2606-4
- Release polkadot-stable2606-5
- Entered the Repository Index: 2,811 stars on 2026-11-11
- Release polkadot-stable2609-2
- Latest push
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 2 Observations, Nov 12, 2026 – Nov 13, 2026. Forks 0. AwesomeRepos saw a new push on 1 of 1 days.
- Nov 13, 2026: new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos reads the weekly commits, the changelog, and the community files each week for the 5,000 visible repositories with the most stars and for each rising repository. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 2 tasks for the maintainers of paritytech/polkadot-sdk.
Improve the Health Facts of the GitHub repository paritytech/polkadot-sdk. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/paritytech/polkadot-sdk. A change to the repository can improve each of the 2 items below. Each item gives the measured fact or score, and a task. 1. The newest release tag is a semantic version Fact: The newest release tag is polkadot-stable2609-2. Rule: The tag of the newest release has the form 1.2.3 or v1.2.3, with an optional pre-release or build part. There is no data when the repository has no release. Task: Make the next release tag a semantic version (1.2.3 or v1.2.3). Do not change or delete a published tag. If a release tool makes the tags, configure it for semantic versions, and write the version scheme in the contributing guide. 2. A licence Fact: GitHub finds no licence. Rule: GitHub finds a licence file. When GitHub cannot name the licence, the fact says so. Task: Ask me which licence to use. Do not choose one yourself. Then add the standard licence text as LICENSE at the root, so that GitHub can name the licence. Do not change the terms. Fill in only the fields of the template (for example the year and the copyright holder), and ask me for a value that you cannot verify. Rules for this work: - Each file must be true for this project. Do not copy text that does not apply to it. - Do not choose a licence, a contact, or a release version for me. Ask me. - Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch. - Keep each change small, and run the checks of this repository before you finish. - At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question). AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts
Maintenance
2 of 4 checks (2 without data)-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
Yes: A push in the last 90 days
Last push on 2026-11-12, 0 days ago. Source
-
No data: Commits in the last 13 weeks
No data: AwesomeRepos has not read the weekly commits.
-
No data: Commits in 26 or more of the last 52 weeks
No data: AwesomeRepos has not read the weekly commits.
Releases
1 of 3 checks (1 without data)-
Yes: A release in the last 365 days
Newest release polkadot-stable2609-2 on 2026-11-12, 1 day ago. 10 or more releases in the last 365 days. Source
-
No: The newest release tag is a semantic version
The newest release tag is polkadot-stable2609-2. Source
-
No data: A changelog file at the root
No data: AwesomeRepos has not scanned this repository.
Security practice
0 of 1 check (1 without data)-
No data: A security policy
No data: AwesomeRepos has not scanned this repository.
AwesomeRepos has not asked OpenSSF Scorecard about this repository.
Community files
0 of 3 checks (2 without data)-
No: A licence
GitHub finds no licence. Source
-
No data: A contributing guide
No data: AwesomeRepos has not scanned this repository.
-
No data: A code of conduct
No data: AwesomeRepos has not scanned this repository.
Dependencies in the index
This section shows the packages that connect this repository to other repositories in the index.
AwesomeRepos has not scanned the dependency graph of this repository yet. The scan reads each visible repository, the most stars first.
21 scanned repositories name a package from this repository.
Uses (in the index) · 0
No data.
Used by (in the index) · 21
-
Cargo: binary-merkle-tree, sp-application-crypto, sp-arithmetic, sp-core and 18 more
-
Cargo: binary-merkle-tree, bp-header-chain, bp-messages, bp-parachains and 204 more
-
Cargo: binary-merkle-tree, cumulus-client-parachain-inherent, cumulus-pallet-parachain-system, cumulus-pallet-parachain-system-proc-macro and 166 more
- QuipNetwork/xquad 5.6K
Cargo: binary-merkle-tree, frame-support, frame-support-procedural, frame-support-procedural-tools and 32 more
-
Cargo: binary-merkle-tree, sc-allocator, sc-chain-spec, sc-chain-spec-derive and 44 more
-
Cargo: polkadot-sdk, sp-crypto-hashing
- use-ink/ink 1.5K
Cargo: binary-merkle-tree, ethereum-standards, frame-benchmarking, frame-support and 50 more
-
Cargo: binary-merkle-tree, cumulus-client-parachain-inherent, cumulus-pallet-parachain-system, cumulus-pallet-parachain-system-proc-macro and 168 more
- paritytech/subxt 491
Cargo: binary-merkle-tree, sc-allocator, sc-executor, sc-executor-common and 30 more
-
Cargo: binary-merkle-tree, bp-asset-hub-rococo, bp-asset-hub-westend, bp-bridge-hub-cumulus and 145 more
Show all 21
-
Cargo: binary-merkle-tree, frame-benchmarking, frame-election-provider-solution-type, frame-election-provider-support and 127 more
-
Cargo: fork-tree, frame-benchmarking, frame-election-provider-support, frame-executive and 172 more
-
Cargo: fork-tree, frame-benchmarking, frame-benchmarking-cli, frame-election-provider-solution-type and 123 more
-
Cargo: fork-tree, frame-benchmarking, frame-benchmarking-cli, frame-executive and 106 more
-
Cargo: binary-merkle-tree, sc-allocator, sc-executor, sc-executor-common and 29 more
-
Cargo: fork-tree, frame-benchmarking, frame-executive, frame-support and 80 more
-
Cargo: sp-core-hashing
-
Cargo: cumulus-pallet-aura-ext, cumulus-pallet-dmp-queue, cumulus-pallet-parachain-system, cumulus-pallet-parachain-system-proc-macro and 230 more
-
Cargo: frame-support, frame-support-procedural, frame-support-procedural-tools, frame-support-procedural-tools-derive and 19 more
-
Cargo: fork-tree, frame-benchmarking, frame-benchmarking-cli, frame-executive and 82 more
-
Cargo: sp-application-crypto, sp-arithmetic, sp-core, sp-core-hashing and 15 more
Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package . A dependency graph also names development packages. deps.dev takes most source repositories from package metadata. How the dependency graph is made
Observations
Latest Observation, Nov 13, 2026: 2,811 stars, 1,260 forks, last push Nov 12, 2026, not archived. One of 2 Observations since Nov 12, 2026.