All integrationsCode Repositories

JSR

Look up JavaScript and TypeScript packages on JSR, the open-source registry from the Deno team.

actions
18
triggers
2

Triggers

Start a workflow when something happens in JSR.

  • JSR New Package VersionTriggers when a package publishes a new version on JSR, optionally only stable releases or only pre-releases, with when it was published, the version before it and how to import it
  • JSR New Package in ScopeTriggers when a package in a scope publishes its first version on JSR, with its description, the runtimes it works on and how to install it

Actions

Steps a workflow can run in JSR.

  • Search packagesFind JSR packages whose name or scope contains some text, such as router or hono, with exact name matches first, optionally only those marked as working on the runtimes you choose. Each result comes with its latest version, description, score and the runtimes it works on. Returns up to 100 packages.
  • Get a packageRead a package: its description, latest version and when it was published, any newer pre-release, how many versions it has, its score, the runtimes it works on, how many packages it depends on and how many depend on it, its GitHub repository, and the commands that install it in Deno or Node.js.
  • Get a package's scoreRead JSR's score for a package and how it was earned, check by check: a README with examples, documented entrypoints and symbols, no slow types, provenance, a description, and the runtimes it is marked as working on.
  • List a package's versionsList the versions a package has published, newest first or by version number, with when each came out, who published it, and whether it is a pre-release, yanked or published with provenance. Narrow it to stable releases or pre-releases, or to a range of publication dates.
  • Get a package versionRead one version of a package: when it was published, whether it is the latest, a pre-release or yanked, its licence, the entrypoints it exports, how many files it holds and their size, and its provenance in the public Sigstore log.
  • List a version's dependenciesList the JSR and npm packages one version of a package imports, with the version range it asks for and the parts of each it uses.
  • Get a version's dependency treeWork out everything one version of a package loads: every JSR package it pulls in, directly or not, at the version that resolves, with how many files and bytes each adds, and the total. npm packages it uses are not included.
  • List a package's dependentsList the packages on JSR that depend on a package, with the versions of each that do, and how many dependents it has altogether.
  • Get a package's downloadsRead how often a package was downloaded over the last 90 days, through JSR itself and through its npm compatibility layer, with totals for the last 7 and 30 days, downloads of its most recent versions and, if you ask, a count for each day.
  • List a version's filesList the files one version of a package publishes, with each file's size and checksum and the version's total size, optionally only paths containing some text.
  • Read a file from a packageRead the text of one file a version of a package publishes, such as its README, deno.json, licence or a source file. Files up to 1 MB can be read, and the first 100,000 characters are returned.
  • List a package's symbolsList the functions, classes, interfaces, types and other symbols the latest version of a package exports, from its documentation on JSR, each with its description and a link to its page. Narrow it by kind, name or entrypoint.
  • Get a scopeRead a scope, the namespace packages are published under such as @std: its description, how many packages it holds and how many of them are published, how many members it has, and when it was created.
  • List a scope's packagesList the packages in a scope, by name, score, newest first or most versions, each with its latest version, description, score and the runtimes it works on. Narrow it to packages that work on the runtimes you choose.
  • List a scope's membersList the people who can publish to a scope, admins first, with their JSR user id, GitHub account id and when they joined.
  • Get a userRead a JSR user's profile, the scopes they are a member of and the packages they published to recently. 'List a scope's members' and 'List a package's versions' give user ids.
  • List new, updated and featured packagesList what JSR's home page shows: the ten packages created most recently, the ten versions published most recently, and the packages JSR features.
  • Get registry statisticsRead how many packages, versions and users JSR has, and how many of each were added in the last day, 7 days and 30 days.

Automate JSR with Lodol.

Connect JSR and ask your AI for your first workflow.

Free plan, no credit card