Sublime Text Package Control Scraper
Pricing
Pay per event
Sublime Text Package Control Scraper
Export the full Sublime Text Package Control catalog (~5,400 packages) with authors, labels, versions, platforms and homepages from the official public channel_v3.json. Fast, no login.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Kaleb Holley
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Export the entire Package Control catalog for Sublime Text (about 5,400 packages) as clean, structured data: name, authors, description, labels, homepage, latest version, platforms, Sublime Text version constraints and download URL.
Data comes from the official public channel_v3.json that the Package Control client itself downloads. No browser, no proxy, no login.
What can it do?
- Full catalog export. Flattens every repository listed in Package Control's channel cache into one dataset.
- Keyword search. Filter by name, description, author, homepage or label (for example
lint,git,theme). - Label filter. Keep only packages tagged with a given Package Control label.
- Sort. Recently updated, name A-Z, or most releases.
- Fast and cheap. One JSON request (~4 MB). Runs in a few seconds on 256 MB.
Use cases
- Plugin authors researching competing Sublime Text packages
- Editor / IDE market research (which categories dominate Package Control)
- Lead lists of open-source Sublime Text developers and their repos
- Finding stale or abandoned packages (sort by
updated) to fork or replace - Scheduled snapshots to track catalog growth over time
Input
| Field | Type | Description |
|---|---|---|
searchQuery | string | Optional keyword. Empty = whole catalog. |
label | string | Keep only packages whose labels contain this text. |
sortBy | updated / name / releases | Result order. |
maxItems | integer | Max results (default 100; set 10000 for the full catalog). |
Example: every linting-related package, most recently updated first:
{ "searchQuery": "lint", "sortBy": "updated", "maxItems": 200 }
Output
{"name": "SublimeLinter","description": "Interactive code linting framework for Sublime Text 3","authors": ["SublimeLinter"],"homepage": "https://github.com/SublimeLinter/SublimeLinter","labels": ["linting"],"readme": "https://raw.githubusercontent.com/SublimeLinter/SublimeLinter/master/README.md","issues": "https://github.com/SublimeLinter/SublimeLinter/issues","donate": null,"previousNames": [],"version": "4.26.1","updatedAt": "2025-01-15 12:00:00","downloadUrl": "https://codeload.github.com/SublimeLinter/SublimeLinter/zip/v4.26.1","platforms": ["*"],"sublimeText": [">=4000"],"releaseCount": 12,"repositoryUrl": "https://packagecontrol.io/repository.json","packageControlUrl": "https://packagecontrol.io/packages/SublimeLinter","scrapedAt": "2026-10-14T11:30:00+00:00"}
Export to JSON, CSV, Excel, XML or HTML, or pull results through the Apify API, webhooks, Make, Zapier or n8n.
Pricing
Free to use right now: you pay only the tiny Apify platform usage of your own run (a full-catalog run uses well under $0.01). Pay-per-result pricing may be added later, with advance notice as Apify requires.
FAQ
Is it legal? The Actor reads only the public, unauthenticated Package Control channel file (channel_v3.json) that every Sublime Text Package Control client downloads. It collects no personal data beyond the public author names listed in each package's channel entry.
How fresh is the data? Fetched live on every run. Package Control regenerates the channel regularly. Schedule the Actor to build a history.
Something broken or a field missing? Open an issue on the Actor's Issues tab.