Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

JSR review

Free#19 of 28 in Package Registries

A free registry for modern ESM packages across JavaScript and TypeScript runtimes.

7.2/10Editor score
Visit JSR
JSR7.2 Visit JSR

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

JSR is an open-source package registry for JavaScript and TypeScript packages. It is designed for developers publishing ESM modules and distributing them across Deno, Node.js, Bun, browsers and Cloudflare Workers. Native TypeScript support, npm-compatible installation and registry APIs make it suitable for teams maintaining modern JavaScript packages that need to reach more than one runtime without changing package format.

Its strongest distinction is the combination of native TypeScript support, cross-runtime consumption and generated API documentation from package source code. Packages can be consumed through native JSR imports or npm-compatible package managers, including npm, pnpm and Yarn. Scoped packages provide member and admin roles, while immutable published versions support fixed package releases. GitHub Actions publishing with OIDC authentication adds a documented workflow for automated releases, and registry, npm compatibility and management APIs support integration with surrounding tooling.

JSR is free to use, including its free plan, according to the vendor’s published pricing information. The registry does not provide private registry functionality, so teams distributing proprietary packages should choose a registry with private-package support instead. Its documented 20 MB limit applies to uploaded packages and individual files. JSR is therefore a strong fit for public JavaScript and TypeScript packages, especially those targeting multiple runtimes and benefiting from generated documentation. It is less suitable for organizations that need private distribution or a package registry spanning multiple package ecosystems.

JSR pros and cons

  • Where it wins
    • Native TypeScript and ESM package publishing
    • Cross-runtime consumption across Deno, Node.js, Bun and more
    • Automatic API documentation and OIDC publishing workflows
  • Where it doesn't
    • No private registry functionality
    • Focused on a single package ecosystem
    • 20 MB limit for uploaded packages and individual files

JSR fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update