JSR Packages Scraper - JavaScript Registry Search & Metadata

Extract package metadata from JSR (JavaScript Registry), the modern package registry for JavaScript and TypeScript runtimes. This Actor searches JSR by keyword and returns structured data for every matching package, including scope, name, description, GitHub source, runtime compatibility, version count, quality score, and latest version. It is built for developers, market researchers, and automation workflows that need clean, up-to-date data from the JSR ecosystem.

Use Cases

• Competitor research — Map packages in a specific JSR niche and compare their scores, version counts, and GitHub presence.
• Dependency auditing — Build inventories of available packages for Deno, Node.js, Bun, Cloudflare Workers, and browser runtimes.
• Catalog generation — Feed JSR package data into internal tools, documentation sites, or market intelligence dashboards.
• Ecosystem monitoring — Track new releases, archived packages, and runtime support trends across the JSR registry.

Input

Field	Type	Required	Description
searchQueries	Array	Yes	Keywords to search on JSR (e.g., oak, hono, deno). Empty input falls back to a curated list of popular queries.
maxItems	Number	Yes	Maximum number of packages to extract across all queries (default: 100).
proxyConfiguration	Object	No	Apify proxy configuration. Included by default for reliable cloud runs.

Output

The Actor outputs a dataset with the following fields for each JSR package:

{
  "scope": "oak",
  "name": "oak",
  "fullName": "oak/oak",
  "description": "A middleware framework for handling HTTP with Deno, Node.js, Bun and Cloudflare Workers.",
  "githubUrl": "https://github.com/oakserver/oak",
  "runtimes": "deno, node, bun, workerd",
  "versionCount": 32,
  "dependencyCount": 0,
  "dependentCount": 0,
  "score": 94,
  "latestVersion": "17.2.0",
  "isArchived": false,
  "updatedAt": "2024-03-01T04:23:01.583Z",
  "createdAt": "2024-01-11T06:10:03.496Z",
  "jsrUrl": "https://jsr.io/oak/oak",
  "error": ""
}

Pricing

Pay per event: $0.001 per package extracted. Charges are calculated only for successful extractions, so you pay for data you can use. Pricing is designed to be competitive with other package registry scrapers on the Apify Store while covering compute and proxy costs.

Limitations

• JSR search results are subject to the JSR public API. Very large result sets may require multiple queries.
• Runtime compatibility is derived from the JSR API response; packages without declared compatibility will return empty values.
• GitHub URLs are only available when the package author has linked a repository.

FAQ

Q: Can I scrape all packages without a search query? A: The Actor uses the JSR search API. Leave searchQueries empty to use a curated set of popular queries, or provide specific keywords to target a niche.

Q: Does the Actor support proxies? A: Yes. Apify proxy is enabled by default to ensure reliable access from cloud runs.

Q: What runtimes are reported? A: The Actor reports any combination of deno, node, bun, browser, and workerd based on the package metadata.

Changelog

• v1.0.0 — Initial release: JSR search, package metadata extraction, and pay-per-event pricing.

---

Built by P. McD0nald for the Apify Store. Open an issue on this Actor's Apify page for support or feature requests.