jsDelivr Package Stats Scraper avatar

jsDelivr Package Stats Scraper

Pricing

from $25.88 / 1,000 results

Go to Apify Store
jsDelivr Package Stats Scraper

jsDelivr Package Stats Scraper

Pull jsDelivr CDN delivery stats for npm and GitHub packages. Returns hits, bandwidth and prior-period values, ranked across day, week, month or year so you can track real-world adoption of any package.

Pricing

from $25.88 / 1,000 results

Rating

0.0

(0)

Developer

ParseForge

ParseForge

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

ParseForge Banner

📊 jsDelivr Package Stats Scraper

🚀 Export real CDN adoption stats in seconds. Pull jsDelivr delivery stats for npm and GitHub packages from a network serving 700+ million daily requests, ranked by hits or bandwidth across day, week, month, year, or sliding windows. No login, no API key, no manual scraping.

🕒 Last updated: 2026-05-15 · 📊 13 fields per record · 🌐 700M+ daily requests · 📦 npm + GitHub sources · 📅 Day / Week / Month / Year

The jsDelivr Package Stats Scraper pulls the official jsDelivr CDN public catalogue and returns 13 fields per package, including package name and source, hits, bandwidth bytes, prior-period values, period-over-period change percentages, and the canonical jsDelivr package page URL. jsDelivr is one of the largest open-source CDNs in the world and is the de facto delivery network for unpkg-style hot-link script tags, ESM imports, and CDN-cached library distribution.

The catalog covers npm packages and GitHub repositories delivered through the network, with stats aggregated across day, week, month, year, sliding month, and sliding year windows, ranked by total hits or total bandwidth. This Actor exports the rankings as CSV, Excel, JSON, or XML, with built-in change-percent calculations so you can track adoption deltas without post-processing.

🎯 Target Audience💡 Primary Use Cases
Open-source maintainers, DevRel teams, web-tooling vendors, supply-chain auditors, package-registry analysts, content marketersReal-world adoption tracking, growth-trend dashboards, competitive benchmarking, "most used libraries" reports, hotlink monitoring

📋 What the jsDelivr Package Stats Scraper does

Five filtering workflows in a single run:

  • 📦 npm packages. Rank delivery stats across the npm-mirrored portion of the network.
  • 🐙 GitHub repositories. Rank delivery stats across gh/ source packages.
  • 🌐 All sources. Combine npm and GitHub rankings in one export.
  • 📅 Period selection. Day, week, month, year, sliding month, or sliding year window.
  • 📊 Rank by hits or bandwidth. Two ways to read "popular": request count or bytes served.

Each record carries the package name, the canonical jsDelivr page URL, the chosen period and rank metric, current and prior-period hits and bandwidth bytes, plus the period-over-period change percentage so you can spot rising and falling packages without doing the math.

💡 Why it matters: download counts on package registries are inflated by CI, mirrors, and Docker pulls. CDN delivery stats reflect what runs in real browsers and on real devices. Building your own pipeline means handling pagination and prior-period diffs. This Actor delivers a clean, ranked dataset on every run.


🎬 Full Demo

🚧 Coming soon: a 3-minute walkthrough showing how to go from sign-up to a downloaded jsDelivr stats dataset.


⚙️ Input

InputTypeDefaultBehavior
maxItemsinteger10Records to return. Free plan caps at 10, paid plan at 1,000,000.
typeenum"npm"npm, gh (GitHub), or any (both).
periodenum"month"Day, week, month, year, sliding month, or sliding year.
byenum"hits"Rank by total hits or total bandwidth bytes served.
datestring""Optional anchor date (YYYY-MM-DD, YYYY-MM, or YYYY). Empty = current period.

Example: top 100 npm packages this month, ranked by hits.

{
"maxItems": 100,
"type": "npm",
"period": "month",
"by": "hits"
}

Example: top 50 GitHub-sourced packages this year, ranked by bandwidth.

{
"maxItems": 50,
"type": "gh",
"period": "year",
"by": "bandwidth"
}

⚠️ Good to Know: stats reflect requests served by jsDelivr only, not the package registry's total install count. A package that's popular in Node-side bundling but rarely hot-linked in browsers may rank lower here than on a registry leaderboard, and that's the signal you want when measuring real-world browser-side adoption.


📊 Output

Each package record contains 13 fields. Download the dataset as CSV, Excel, JSON, or XML.

🧾 Schema

FieldTypeExample
📦 namestring"jquery"
🔗 urlstring"https://www.jsdelivr.com/package/npm/jquery"
📂 typestring"npm"
📅 periodstring"month"
📊 rankBystring"hits"
📈 hitsnumber | null4521234567
📈 bandwidthBytesnumber | null382451234567
📈 previousHitsnumber | null4221345678
📈 previousBandwidthBytesnumber | null364123456789
📊 hitsChangePctnumber | null7.11
📊 bandwidthChangePctnumber | null5.03
🕒 scrapedAtISO 8601"2026-05-15T00:00:00Z"
errorstring | undefined(only when a record fails)

📦 Sample records


✨ Why choose this Actor

Capability
🌐700M+ daily requests of signal. Real browser-side adoption data, not registry install counts.
📦npm + GitHub coverage. Rank both registries side by side in a single run.
📅Six period windows. Day, week, month, year, sliding month, sliding year.
📊Two rank metrics. Sort by hits to count requests, or by bandwidth to count bytes shipped.
📈Built-in change-percent. Period-over-period delta calculated for both hits and bandwidth.
Fast. 100 records in under 5 seconds, 10,000 in under a minute.
🚫No authentication. Works on the public jsDelivr stats catalogue. No token required.

📊 CDN delivery stats are the cleanest public signal for browser-side library adoption, and jsDelivr serves more than 700 million requests per day across the open-source ecosystem.


📈 How it compares to alternatives

ApproachCostCoverageRefreshFiltersSetup
⭐ jsDelivr Package Stats Scraper (this Actor)$5 free credit, then pay-per-usenpm + GitHub, full networkLive per runtype, period, rank metric, anchor date⚡ 2 min
Registry download countsFreePer-registryDailyNone🐢 Per-package only
Hand-built CDN dashboardsFreeCustomManualNone⏳ Days
Paid analytics SaaS$$Per-toolStreamingVendor-defined🕒 Hours

Pick this Actor when you want browser-side adoption truth, ranked across periods, with prior-period deltas baked in.


🚀 How to use

  1. 📝 Sign up. Create a free account with $5 credit (takes 2 minutes).
  2. 🌐 Open the Actor. Go to the jsDelivr Package Stats Scraper page on the Apify Store.
  3. 🎯 Set input. Pick a source (npm, gh, or any), period, rank metric, and maxItems.
  4. 🚀 Run it. Click Start and let the Actor collect your data.
  5. 📥 Download. Grab your results in the Dataset tab as CSV, Excel, JSON, or XML.

⏱️ Total time from signup to downloaded dataset: 3-5 minutes. No coding required.


💼 Business use cases

📊 Open-source maintainers and DevRel

  • Track real adoption of your library month over month
  • Build investor / sponsor decks with public CDN data
  • Compare your package against direct competitors
  • Spot version-bump impact in delivery stats

🛡️ Supply-chain auditors

  • Identify which CDN libraries actually run in production
  • Surface long-tail packages on the rise
  • Cross-reference popularity with vulnerability databases
  • Build "most-served on the network" priority lists

📰 Content and editorial

  • "Most popular JavaScript libraries this month" round-ups
  • Year-end ecosystem retrospectives
  • Trend pieces on emerging frontend tools
  • Embedded leaderboards on dev-news sites

🧑‍💻 Tooling vendors

  • Default-package suggestions in editors
  • "Try this CDN URL" copy buttons
  • Usage-weighted recommendation engines
  • Telemetry baselines for your customer dashboards

🔌 Automating jsDelivr Package Stats Scraper

Control the scraper programmatically for scheduled runs and pipeline integrations:

  • 🟢 Node.js. Install the apify-client NPM package.
  • 🐍 Python. Use the apify-client PyPI package.
  • 📚 See the Apify API documentation for full details.

The Apify Schedules feature lets you trigger this Actor on any cron interval. Daily and weekly refreshes keep your adoption dashboard current without manual pulls.


🌟 Beyond business use cases

CDN delivery data powers more than commercial workflows. The same structured records support research, education, civic projects, and personal initiatives.

🎓 Research and academia

  • Empirical web-engineering studies of library adoption
  • Reproducible "most-used JavaScript" datasets
  • Coursework on CDN economics and delivery
  • Long-term cross-period adoption analyses

🎨 Personal and creative

  • Hobbyist leaderboard pages for fun
  • Portfolio-grade adoption dashboards
  • Twitter/Mastodon "weekly top-10" bots
  • Side-project package directories

🤝 Non-profit and civic

  • Open-source ecosystem health reports
  • Foundation-led "what's running in production" surveys
  • Investigative journalism on web-platform shifts
  • Public-broadcast adoption transparency

🧪 Experimentation

  • Train ML models on adoption time series
  • Prototype recommendation systems for libraries
  • Build agent pipelines that audit CDN usage of a site
  • Validate visualization concepts with live data

🤖 Ask an AI assistant about this scraper

Open a ready-to-send prompt about this ParseForge actor in the AI of your choice:


❓ Frequently Asked Questions

🧩 How does it work?

Pick a source (npm, GitHub, or both), a period (day to year, plus sliding windows), and a rank metric (hits or bandwidth). The Actor pulls the matching ranking and emits one clean structured record per package, with prior-period values and change percents already calculated.

📊 What's the difference between hits and bandwidth?

Hits is the count of requests served. Bandwidth is the total bytes shipped. A small library hot-linked everywhere will dominate hits; a large library used on fewer sites can still dominate bandwidth.

📅 How are periods defined?

day, week, month, and year align to calendar boundaries. s-month and s-year are sliding windows ending at the anchor date (defaults to today). For historical lookups, set date to a specific YYYY-MM-DD, YYYY-MM, or YYYY anchor.

📦 What's the difference between npm and GitHub sources?

npm rankings cover packages mirrored from the npm registry. gh rankings cover repositories served via the network's gh/owner/repo paths. Some libraries appear in both. Set type: "any" to combine.

🔁 How often are stats refreshed?

The catalogue updates continuously as the network serves traffic. Every Actor run pulls the latest ranking.

📈 Can I track period-over-period growth?

Yes. Every record includes previousHits, previousBandwidthBytes, hitsChangePct, and bandwidthChangePct so you can spot rising and falling packages with no extra math.

⏰ Can I schedule regular runs?

Yes. Use Apify Schedules to refresh the rankings daily, weekly, or hourly and keep your downstream dashboard or alerter in sync.

The jsDelivr stats catalogue is publicly accessible. Always credit jsDelivr when you redistribute the data verbatim. Review the downstream terms of your specific use case.

💼 Can I use this data commercially?

Yes. The underlying delivery stats are public. Always credit the source on redistribution.

💳 Do I need a paid Apify plan to use this Actor?

No. The free Apify plan is enough for testing and small runs (10 records per run). A paid plan lifts the limit and gives you access to scheduling, higher concurrency, and larger datasets.

🔁 What happens if a run fails or gets interrupted?

Apify automatically retries transient errors. If a run still fails, you can inspect the log in the Runs tab, fix the input, and re-run. Partial datasets from failed runs are preserved so you never lose progress.

🆘 What if I need help?

Our support team is here to help. Contact us through the Apify platform or use the Tally form linked below.


🔌 Integrate with any app

jsDelivr Package Stats Scraper connects to any cloud service via Apify integrations:

  • Make - Automate multi-step workflows
  • Zapier - Connect with 5,000+ apps
  • Slack - Get weekly top-10 leaderboards in your channels
  • n8n - Drop runs into self-hosted workflows
  • Pipedream - Trigger event-driven pipelines
  • Airbyte - Pipe CDN stats into your warehouse
  • GitHub - Trigger runs from commits and releases
  • Google Drive - Export datasets straight to Sheets

You can also use webhooks to trigger downstream actions when a run finishes. Push the weekly leaderboard to Notion, refresh the adoption widget on your library's docs site, or alert the team in Slack when a competitor jumps into the top 10.


💡 Pro Tip: browse the complete ParseForge collection for more reference-data scrapers.


🆘 Need Help? Open our contact form to request a new scraper, propose a custom data project, or report an issue.


⚠️ Disclaimer: this Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by jsDelivr, Prospect One, the Open Source Collective, or any of its contributors. All trademarks mentioned are the property of their respective owners. Only publicly available open CDN stats are collected.