🦕 Deno Land X Modules Scraper

🚀 Export the deno.land/x module registry in one run. Pull module names, GitHub stars, latest versions, full version history, and source repos straight from the official apiland API.

🕒 Last updated: 2026-06-08 · 📊 Up to 16 fields per record · live registry · one record per module

Turn the deno.land/x third party registry into clean, structured records you can drop into a dependency tracker, a package explorer, or a research notebook. List the exact modules you care about, or leave the field empty and page through the entire registry. Each record carries the GitHub star count, popularity score, latest version, the full version list, the upload timestamp of the latest release, and the GitHub repository the module is published from.

Coverage is the public deno.land/x registry as the apiland API serves it: every module's metadata, its complete version history, and the source repository behind it. No Deno account, no key, and no login are required.

🎯 Target Audience	💡 Primary Use Cases
Deno developers and library authors	Track versions and stars across dependencies
Platform and DevOps engineers	Audit third party modules used in a codebase
Ecosystem researchers and analysts	Map registry growth and module popularity
Tooling and dashboard builders	Seed a package explorer with live metadata

📋 What the Deno Land X Modules Scraper does

This Actor calls the public apiland API behind deno.land/x and returns one clean record per module:

• Identity — module name, description, and the canonical deno.land/x URL.
• Popularity — GitHub star count, popularity score, and registry tags.
• Versions — latest version, total version count, and the full version list.
• Provenance — the GitHub repository, optional subdirectory, and the upload timestamp of the latest release.

You either pass a list of module names or browse the whole registry, and you control how many records come back. Every record carries a scrapedAt timestamp.

🎬 Full Demo (🚧 Coming soon)

⚙️ Input

Field	Type	Description
modules	array	Exact module names to scrape, for example oak, zod, or std. Leave empty to browse the whole registry.
includeVersions	boolean	When on, each record includes the full version list. The latest version and its upload timestamp are always returned. Defaults to true.
maxItems	integer	How many records to return. Free plan is capped at 10.

Example 1 — specific modules with full version history

{
    "modules": ["oak", "zod", "std"],
    "includeVersions": true,
    "maxItems": 3
}

Example 2 — browse the registry, latest version only

{
    "includeVersions": false,
    "maxItems": 100
}

⚠️ Good to Know: the registry list endpoint omits the source repository, so for browse runs the Actor fetches each module's latest version metadata to fill in the GitHub repo and upload timestamp. That means one extra request per module, which is normal and keeps every record complete.

📊 Output

Each module record looks like this:

Field	Description
📦 name	deno.land/x module name
📝 description	Module description
⭐ starCount	GitHub star count
📈 popularityScore	Registry popularity score
🏷 latestVersion	Newest published version
🔢 versionCount	Number of published versions
📅 latestVersionUploadedAt	Upload timestamp of the latest version
🐙 repository	GitHub owner/repo slug
🔗 repositorySource	Full GitHub repository URL
📁 repositorySubdir	Subdirectory the module is published from, if any
🗂 tags	Registry tags, for example top_1_percent
🌐 url	Canonical deno.land/x page
🛰 registryApiUrl	apiland API URL for the module
📜 versions	Full list of published versions (when enabled)
🕒 scrapedAt	Collection timestamp
❌ error	Null on success

Real sample — oak

{
    "name": "oak",
    "description": "A middleware framework for handling HTTP with Deno, Node, Bun and Cloudflare Workers 🐿️ 🦕",
    "starCount": 4731,
    "popularityScore": 180462,
    "latestVersion": "v17.2.0",
    "versionCount": 103,
    "latestVersionUploadedAt": "2025-11-22T01:00:22.287Z",
    "repository": "oakserver/oak",
    "repositorySource": "https://github.com/oakserver/oak",
    "repositorySubdir": null,
    "tags": ["top_1_percent"],
    "url": "https://deno.land/x/oak",
    "registryApiUrl": "https://apiland.deno.dev/v2/modules/oak",
    "versions": ["v17.2.0", "v17.1.6", "v17.1.5", "v17.1.4"],
    "scrapedAt": "2026-06-08T17:43:16.007Z",
    "error": null
}

Real sample — zod

{
    "name": "zod",
    "description": "TypeScript-first schema validation with static type inference",
    "starCount": 19572,
    "popularityScore": 117073,
    "latestVersion": "v3.25",
    "versionCount": 82,
    "latestVersionUploadedAt": "2025-05-21T00:10:18.916Z",
    "repository": "colinhacks/zod",
    "repositorySource": "https://github.com/colinhacks/zod",
    "repositorySubdir": "deno/lib/",
    "tags": ["top_1_percent"],
    "url": "https://deno.land/x/zod",
    "registryApiUrl": "https://apiland.deno.dev/v2/modules/zod",
    "versions": ["v3.25", "v3.24.4", "v3.24.3", "v3.24.2"],
    "scrapedAt": "2026-06-08T17:43:16.352Z",
    "error": null
}

Real sample — std

{
    "name": "std",
    "description": "The Deno Standard Library",
    "starCount": 2565,
    "popularityScore": 615,
    "latestVersion": "0.224.0",
    "versionCount": 190,
    "latestVersionUploadedAt": "2024-04-25T03:01:10.742Z",
    "repository": "denoland/deno_std",
    "repositorySource": "https://github.com/denoland/deno_std",
    "repositorySubdir": null,
    "tags": [],
    "url": "https://deno.land/x/std",
    "registryApiUrl": "https://apiland.deno.dev/v2/modules/std",
    "versions": ["0.224.0", "0.223.0", "0.222.1", "0.222.0"],
    "scrapedAt": "2026-06-08T17:43:16.650Z",
    "error": null
}

✨ Why choose this Actor

• One clean record per module, with consistent field names that map onto a database schema.
• Two ways to run, by name list or full registry browse, from a single input.
• Version history and the latest upload timestamp come ready, not buried behind extra calls.
• The GitHub source repository is resolved for every record, even in browse mode.
• No Deno account, no key, and no login required.

📈 How it compares to alternatives

Approach	Effort	Structured fields	Version history	Maintenance
This Actor	One run	Yes	Yes	None on your side
Browsing deno.land/x by hand	Hours	Inconsistent	Manual	Constant
Writing your own apiland client	Days	Depends	Manual	You own the upkeep

🚀 How to use

1. Create a free Apify account using this sign-up link.
2. Open the Deno Land X Modules Scraper.
3. Add module names to modules, or leave it empty to browse the registry.
4. Set maxItems and toggle includeVersions to taste.
5. Click Start and grab your results when the run finishes.

💼 Business use cases

Dependency management

Goal	How this helps
Audit third party modules in a project	Pull stars, latest version, and source repo for each
Spot stale dependencies	Compare latestVersion and latestVersionUploadedAt

Developer tooling

Goal	How this helps
Build a package explorer	Seed it with live registry metadata
Power an upgrade checker	Track version counts and newest releases

Ecosystem research

Goal	How this helps
Measure registry growth	Browse the full module list on a schedule
Rank modules by reach	Sort by star count and popularity score

Content and reporting

Goal	How this helps
Write a "top Deno modules" roundup	Use real stars and popularity scores
Track a module's release cadence	Read its full version list and timestamps

🔌 Automating Deno Land X Modules Scraper

Connect runs to the tools you already use:

• Make and Zapier to trigger runs and route records into sheets or databases.
• Slack to post a summary when a run finishes.
• Airbyte to load results into a warehouse.
• GitHub Actions to schedule periodic snapshots.
• Google Drive to archive each run's output.

🌟 Beyond business use cases

• Research: study how the Deno module ecosystem grows over time.
• Personal: keep a watchlist of your favorite Deno libraries.
• Non-profit: maintain a community list of vetted modules.
• Experimentation: prototype a registry dashboard without writing a scraper.

🤖 Ask an AI assistant

Paste your results into ChatGPT, Claude, Perplexity, or Microsoft Copilot and ask it to rank modules by stars, group them by repository owner, or flag dependencies that have not shipped a release in a while.

❓ Frequently Asked Questions

Do I need a Deno or GitHub account? No. The Actor reads the public apiland API behind deno.land/x, which needs no login.

Do I need an API key? No key is required.

Can I scrape the whole registry? Yes. Leave modules empty and the Actor pages through every module up to your maxItems.

Can I target specific modules? Yes. List exact names like oak, zod, or std in the modules field.

Where does the star count come from? It is the GitHub star count for the module's source repository, as reported by the registry.

What is the popularity score? A ranking value the registry computes from recent traffic. The Actor passes through what the source provides.

Do I get every published version? Yes when includeVersions is on. The latest version and its upload timestamp are always included.

Why is repositorySubdir sometimes null? Some modules publish from the repository root, so there is no subdirectory. Others, like zod, publish from a path such as deno/lib/.

How fresh is the data? Each run pulls live from the registry, so it reflects the catalog at run time.

Can I schedule this? Yes. Use Apify Schedules to snapshot the registry on any cadence.

🔌 Integrate with any app

Results are available through the Apify API, so you can pull them into any app, database, or workflow you already run.

🔗 Recommended Actors

• Have I Been Pwned Breaches Catalog Scraper
• Brawlify Brawl Stars Database Scraper
• More developer and reference data Actors in the ParseForge collection

💡 Pro Tip: browse the complete ParseForge collection.

🆘 Need Help? Open our contact form

⚠️ Disclaimer: independent tool, not affiliated with Deno or the Deno Land authors. Only publicly available data is collected.