Deno Land X Modules Scraper

Deno Land X Modules Scraper

Scrape module metadata from the deno.land/x registry, from specific packages or the entire catalog. Every record includes the module name, description, star count, and latest version. Export to CSV, JSON, Excel, or XML.

The deno.land/x registry is the standard library for Deno modules, but browsing it manually or through the website gives you no way to export structured data. This actor reads the public registry pages directly, collecting module names, descriptions, star counts, and version histories. You can target specific modules by name or page through the whole catalog, and the output is a clean, flat dataset ready for analysis.

Who uses it	What they scrape Deno Land X for
Deno developers	Audit dependencies across projects by pulling metadata for a list of module names.
DevTool builders	Populate a searchable internal catalog of available Deno modules with star counts and descriptions.
Security researchers	Track version histories of specific modules to identify outdated or unmaintained packages.
Data analysts	Analyze trends in the Deno ecosystem by scraping the entire registry and charting module growth over time.

What it does

This Actor collects module metadata from the deno.land/x registry and returns each module as a flat row with its name, description, stars, and version information.

• 📋 Targeted scraping: Provide a list of exact module names like 'oak' or 'zod' and get only those records back.
• 🌐 Full registry browsing: Leave the module list empty to page through every public module on deno.land/x.
• 🕒 Version history control: Toggle full version lists on to see every published version and the latest upload timestamp, or off for the current version.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with Deno Land X data

📦 Audit your project dependencies.

A Deno developer feeds a list of module names from their import map and checks the latest version and star count for each to decide which ones to upgrade or replace.

🔍 Build a custom module search engine.

A platform team scrapes the full registry weekly, stores the name, description, and stars, and powers an internal search tool for their engineering org.

📊 Analyze Deno ecosystem trends.

A data analyst runs the actor monthly against the whole registry, tracks star growth and new module creation, and reports on which categories are gaining traction.

🛡️ Identify unmaintained packages.

A security engineer scrapes a list of critical modules with full version history and flags any that have not published a new version in over a year.

Why choose this scraper

	What you get
Structured output	Every module comes back as a flat row with a fixed schema, ready for CSV, JSON, Excel, or XML export.
No API key needed	Reads the public deno.land/x website directly, so there is no registration or token to manage.
Version tracking	Optionally pull the complete version history for each module, including upload timestamps.
Scalable collection	Collect up to a million modules per run, from a handful of names to the entire registry.

How it compares

No other Store actor targets Deno Land X the same way, so the honest comparison is with the alternatives teams actually weigh.

	Deno Land X Modules Scraper	Build it in-house	By hand
Setup	Run it now, zero config	Days of engineering	None, but hours per pull
When Deno Land X changes	Maintained for you	You fix it	You re-learn the page
Proxies, retries, anti-bot	Built in	Your problem	Browser only
Output	Fixed JSON schema, CSV/Excel export	Whatever you build	Copy-paste
Cost	Pay per result	Engineering time	Analyst hours

Configure the run

Drive the Actor with a list of exact module names or leave it empty to scrape the whole registry, and set a maximum number of modules to collect per run. The Input tab lists every parameter.

A first run with the defaults:

{
 "modules": [
 "oak",
 "zod"
 ],
 "maxItems": 10
}

A larger pull:

{
 "modules": [
 "oak",
 "zod"
 ],
 "maxItems": 200
}

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the Deno Land X Modules Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to Deno Land X through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/deno-land-x-modules-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check that the module names you entered are spelled exactly as they appear on deno.land/x. Module names are case-sensitive. If you left the list empty, the registry listing page structure may have changed; try running again later or contact support.

The actor is timing out before collecting all modules.

Lower the maximum modules limit to a smaller number and run the actor multiple times, or increase the run timeout in your Apify actor settings.

Some modules are missing their star count or description.

The deno.land/x registry pages may not always display every field. If a module has no stars or description on the website, those fields will be empty in your dataset.

I get an error about the website being unreachable.

This is usually a temporary network issue or a block from the target site. Wait a few minutes and retry the run. If it persists, consider using Apify proxies to route your requests.

FAQ

Question	Answer
Can I scrape the entire deno.land/x registry?	Yes. Leave the module names list empty and set a high maximum modules limit. The actor will page through the registry listing and return every public module it finds.
What data do I get for each module?	Each row includes the module name, description, star count, latest version string, and optionally the full list of published versions with the upload timestamp of the most recent one.
Do I need a Deno account or API key?	No. The actor reads the public deno.land/x website pages, so no authentication, API registration, or token is required.
How do I scrape only a few specific modules?	Add the exact module names to the module names input field, for example 'oak' and 'zod'. The actor will fetch only those modules and skip the rest of the registry.
Can I get the version history for a module?	Yes. Turn on the 'Include full version history' option and each record will contain a list of all published versions along with the timestamp of the latest upload.
What output formats are supported?	You can export your dataset in CSV, JSON, Excel, or XML formats from the Apify platform.
How many modules can I scrape in one run?	You can set the maximum modules limit up to 1,000,000 per run. The actor will stop once it reaches that count.
Does this actor scrape module source code?	No. It collects only the metadata shown on the deno.land/x registry pages: name, description, stars, and version information. It does not download or store source code.
Is this actor affiliated with Deno Land Inc.?	No. This is an independent community scraper that reads publicly available web pages. It is not built or endorsed by Deno Land Inc.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Deno Land Inc. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.