CocoaPods/Specs: the master repo of public podspecs, and what it does not hand you
The CocoaPods Master Repo
At a glance
- What is it?
- CocoaPods/Specs is the public index of CocoaPods specifications, under MIT, with pushes still landing in November 2026. It is data rather than a tool, its README is three links and a license line, and its only release is a 2016 snapshot.
- Who is it for?
- CocoaPods/Specs matters to Cocoa developers who publish pods or need to inspect the public specification for one, and to anyone auditing what the CocoaPods index says about a dependency. It is not something to clone as a library, and its 2016 release is not a current copy.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- CocoaPods/Specs6,820 ★ · +2
| Repository | 2026-08-21 | 2026-11-15 |
|---|---|---|
| CocoaPods/Specs | 6.8k | 6.8k |
2 Stars in the last 86 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
A repository of public podspecs, not a library you install
CocoaPods/Specs calls itself The CocoaPods Master Repo. It holds the public specifications for CocoaPods, the dependency manager whose own code lives in the separate CocoaPods/CocoaPods repository. A specification, or Podspec, is the file that describes a pod; this repository is where the public ones are collected, under the Specs/ directory at the top of the tree.
That distinction shapes how you approach it. There is no install command and no package to add to a project. You do not write code against this repository. It is an index that the CocoaPods tool consults, and that people browse when they want to see exactly what a published pod declares. GitHub reports no primary language for it, which fits a repository that is mostly specification data rather than an application. The default branch is master, and the homepage is cocoapods.org. If you came here looking for how to install CocoaPods itself, this is the wrong repository; the tool is in CocoaPods/CocoaPods.
Getting a pod listed starts with a Trunk account
The README points pod authors to two guides on guides.cocoapods.org. One, Specs and the Specs Repo, covers creating Podspecs and how the Spec repo works. The other, Getting setup with Trunk, covers creating a CocoaPods user account. Trunk is the name CocoaPods gives to that account system.
The consequence for a first-time author is that publishing is a process with an account at its front, not a matter of editing a file in this repository and walking away. Before your pod can appear in the master repo, you need that Trunk account set up, and you need a Podspec that follows the format the Specs guide explains. Neither guide is reproduced in this repository, so the README gives you no offline copy of the steps. If guides.cocoapods.org is unavailable, the repository alone will not tell you how to submit.
The only release is a snapshot from 19 October 2016
The Releases page holds exactly one entry, tagged 20161019 and titled Snapshot of the repo on the 19th of October 2016, published on 2016-10-19. Meanwhile the repository keeps receiving pushes; the most recent was on 2026-11-03.
That gap of ten years is the trap. Someone who reaches for the release because it looks like the official downloadable version gets an index frozen in 2016. Every pod version published since then is missing from it, and any specification that changed afterwards appears in its 2016 form. The snapshot has value as a historical record of what the index looked like on that date, for instance when reconstructing an old build. For anything current, the master branch is the source, and the release tag should be treated as an archive rather than a distribution.
Ruby tooling and lint configuration sit beside the specs
Specs/ is not alone at the top level. The repository also carries a Gemfile and Gemfile.lock, a .rubocop.yml lint configuration, a Scripts/ directory, a .github/ directory, and a file named CocoaPods-version.yml. These are the pieces that keep a large shared index in order rather than parts of any single pod.
For a contributor, the Gemfile.lock means the repository pins the exact Ruby gem versions its own tooling expects, so running anything from Scripts/ locally means installing those gems rather than whatever happens to be on your machine. The presence of .github/ means automation runs on the repository itself. The README does not explain what each script does or what CocoaPods-version.yml controls, so anyone planning to run or change that tooling has to read the files directly before touching them.
Search indexing and site deployment config live in the same tree
Two more top-level files point beyond the specifications. AlgoliaSearch.yml is named for Algolia, a hosted search service, and netlify.toml is the configuration file name used by Netlify, a site hosting platform. Their presence means the repository is wired to more than the CocoaPods command line tool: there is configuration here for search and for a deployed site.
The practical point for readers is narrow. These files belong to the people who run the index, not to pod authors, and a change to a Podspec does not require touching them. They also explain why the repository holds configuration files that have nothing to do with any individual pod. The README does not describe what either file configures or which site the Netlify configuration deploys, so treat them as infrastructure you can read but have no reason to edit as a contributor.
The README defers every rule to guides.cocoapods.org
The README is short: a one-line statement that this repository contains the public CocoaPods specifications, two links, and a license line. Everything about how a Podspec must be written, how submissions are checked, and how accounts work sits in the external guides rather than in the repository.
This has a cost for anyone working from the repository alone. You can read thousands of existing specifications under Specs/ and copy their shape, but the README does not state the rules those files are checked against, and it does not explain how the directory under Specs/ is organised. Inferring the format from examples works until you hit a case the examples do not cover. The safer route for authors is to read the Specs and the Specs Repo guide first and treat existing files as illustrations, not as the specification. For readers auditing a dependency, the files themselves are the ground truth for what was published, whatever the guide says should be there.
MIT covers both the specifications and CocoaPods
The license line is one sentence: the specifications and CocoaPods are available under the MIT license. That covers the Podspec files collected here, not only the CocoaPods tool.
For anyone building on the index, for example mirroring it internally or analysing it, this is the part of the README with direct legal weight, and it is permissive. It does not say anything about the source code of the pods themselves. A Podspec points at a pod's code, but the pod's own license is whatever its author chose, and the MIT line here applies to the specification file, not to the library it describes. Teams checking the licenses of their dependencies still need to look at each pod's own terms rather than stopping at the master repo's license.
Editorial conclusion
CocoaPods/Specs matters to Cocoa developers who publish pods or need to inspect the public specification for one, and to anyone auditing what the CocoaPods index says about a dependency. It is not something to clone as a library, and its 2016 release is not a current copy. Before relying on it, read the Specs and the Specs Repo guide and the Trunk setup guide on guides.cocoapods.org, because the repository itself carries almost no instructions.
Frequently asked questions
What is meant by Specs in CocoaPods/Specs?
Specs is short for specifications. CocoaPods/Specs holds the public CocoaPods specifications, the Podspec files that describe each published pod.
Is it the CocoaPods Spec repo or the Specs repo?
The repository is named CocoaPods/Specs and calls itself The CocoaPods Master Repo, while the CocoaPods guide is titled Specs and the Specs Repo and also refers to it as the Spec repo.
What is CocoaPods/Specs short for?
It stands for CocoaPods specifications. The repository contains the public specifications under its Specs/ directory, available under the MIT license.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/cocoapods-specs)Star history chart for your README
[](https://hysenlabs.com/projects/cocoapods-specs)Was this useful?