GitStar
TrendingExploreTop 100Insight
⌘K
GitStar

A ranking dashboard for GitHub momentum, durable repository leaders, package adoption, and editorial context.

Data source · GitHub API and package ecosystem snapshots

Home

HomeTrendingMomentumPulseExplore

Discover

CategoriesLanguagesOrganizationsAI / MLMCP

Workflow

CompareWatchlistRandom

Knowledge

InsightGuideMethodology

Support

FAQAbout GitStarContactPrivacyTerms

© 2026 GitStar. All rights reserved.

Data sourced from GitHub API

  1. Home
  2. Organizations
  3. OpenZeppelin
OpenZeppelinOrganization

OpenZeppelin

@openzeppelin • The standard for secure blockchain applications. Use this route to separate flagship concentration from portfolio breadth before you treat a publisher as broadly strong.

Portfolio concentration

86%

Top three share

Shows whether the organization is driven by one breakout repo or several visible projects.

Breadth

29 repos

Visible snapshot

24 repositories updated in the last 90 days.

Leading language

TypeScript

Portfolio mix

TypeScript (11), Unknown (5), Rust (4)

Average size

9

Stars per repository

Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.

Back to organizationsCompare repositories
Updated: 2026-07-22(11d ago)GitHub API fallback29 repositories

Portfolio Shape

86%

of the visible star count comes from this organization's top three repositories.

Average Repository Size

9

stars per repository in this same snapshot.

Current Mix

TypeScript

is the most common language here, with 24 repositories updated in the last 90 days.

Why this rank

This organization stands out because one flagship repo drives 82% of its visible star count.

Flagship share 82%Breakout repo: openzeppelin-skills

Organization pages work best when you separate portfolio breadth from flagship concentration. In OpenZeppelin's case, the visible top three repositories account for about 86% of total stars in this snapshot, which helps explain whether the organization is known for one breakout project or for a broader repeatable portfolio.

The dominant language mix here is TypeScript (11), Unknown (5), Rust (4). That makes this page useful not just for popularity checks, but also for seeing what technical shape an organization's public ecosystem actually has.

Source: GitHub API fallback. This is the same cache-first snapshot used by the organization ranking list, so the summary view and the detail view should stay aligned.

Top Repositories

#RepositoryLanguageStars🍴 ForksUpdated
1openzeppelin/openzeppelin-skills

Agent skills for secure smart contract development with OpenZeppelin Contracts libraries

203282 weeks ago
2openzeppelin/Robust-Provider

Timeout-aware, auto-retrying, failover-ready RPC provider wrapper for Alloy built in Rust

Rust644 days ago
3openzeppelin/openzeppelin-ui

OpenZeppelin UI - React components and utilities for blockchain applications

TypeScript52Yesterday
4openzeppelin/cairo-pq-verifiers

Post Quantum verifiers candidates for a custom Account implementation on Starknet

Cairo431 weeks ago
5openzeppelin/canton-stablecoin

Stablecoin DAML with single admin CDP + fixed-discount liquidation

Shell431 weeks ago
6openzeppelin/daml-lint

Static analysis scanner for DAML contracts

Rust422 months ago
7openzeppelin/daml-props

Property-based testing for DAML contracts

311 months ago
8openzeppelin/canton-token-template

DAML template for CIP-056, Canton Token Standard

Shell311 weeks ago
9openzeppelin/relayer-plugin-x402-facilitator

OpenZeppelin Relayer - x402 Facilitator plugin

TypeScript324 months ago
10openzeppelin/hardhat-tronJavaScript225 days ago
11openzeppelin/tron-contractsSolidity202 days ago
12openzeppelin/openzeppelin-sui-payments

Closed-loop stablecoin payments and loyalty dApp template on Sui (Permissioned Asset Standard). Reference implementation: Joe's Coffee.

TypeScript206 days ago
13openzeppelin/rust-project-templateRust20Yesterday
14openzeppelin/canton-contractsShell102 days ago
15openzeppelin/openzeppelin-adapters

OpenZeppelin Ecosystem Adapters are a set of modular, chain-specific integration packages that bridge the gap between blockchain ecosystems and developer tooling.

TypeScript116 days ago
16openzeppelin/daml-verify

Formal verification for DAML contracts

Python111 months ago
17openzeppelin/rwa-wizard

Wizard-based configuration interface for real-world asset token projects across multiple blockchain ecosystems.

TypeScript11Yesterday
18openzeppelin/openzeppelin-sui-ammTypeScript126 days ago
19openzeppelin/tron-runtime

tron runtime

TypeScript001 weeks ago
20openzeppelin/openzeppelin-foundry-upgrades-tron

TRON (TVM) support for OpenZeppelin Foundry Upgrades.

TypeScript005 days ago
21openzeppelin/tron-upgrades

OpenZeppelin Upgrades Plugins for TRON (TVM) — Hardhat and TronBox. Monorepo.

TypeScript005 days ago
22openzeppelin/canton-specsShell002 days ago
23openzeppelin/tron-contracts-upgradeableSolidity002 days ago
24openzeppelin/relayer-channels-infra

OpenZeppelin relayer channels IaC

TypeScript011 months ago
25openzeppelin/canton-dev-fund

Canton Development Fund proposals, reviews, and administration

003 months ago
26openzeppelin/mRWA-protocol003 months ago
27openzeppelin/oif-solver

Open-source solver implementation, tooling, and libraries to easy start filling cross-chain intents.

Rust003 weeks ago
28openzeppelin/broadcaster-proof-service

Cross-chain storage proof generation API for the [OIF Solver](https://github.com/openzeppelin)'s Broadcaster settlement.

TypeScript004 months ago
29openzeppelin/setup-compact-action

Github Action for installing Compact compiler

007 months ago

Next step after the organization read

Open a flagship repository, compare a couple of portfolio leaders, or return to the organization map when you want a broader concentration read.
Open flagship repoCompare repositoriesBack to organizations

Learn and methodology

Keep trust-building context reachable, but behind the first data read instead of ahead of it.
GuideMethodologyArticlesWeekly Digest

How to read this organization snapshot

Total stars are useful as a discovery signal, but they do not tell you whether a team maintains every repository equally. Pair this page with release cadence, maintainer activity, and the flagship concentration shown above before making adoption decisions.

For broader background on GitStar's ranking logic and editorial guidance, see Methodology & Editorial Standards.