All integrationsCode Repositories

Repology

Track the versions of free software packaged across hundreds of Linux and BSD distributions, Homebrew, nixpkgs and language registries with Repology.

actions
8
triggers
4

Triggers

Start a workflow when something happens in Repology.

  • New version on RepologyRuns when a new version of a project appears in any repository Repology tracks, usually within hours of the first one packaging the release. Stable releases only, or development ones too.
  • Repology package outdated or updatedRuns when one repository's package of a project changes: when a newer version elsewhere leaves it outdated, when the repository updates it, or on any change, including the package being added or removed.
  • New change in a Repology repositoryRuns for each change Repology records in a repository, or in one maintainer's packages there: a package added or removed, updated to the newest version, or left outdated by a newer one. Optionally only one kind of change or one project.
  • New Repology problemRuns when Repology finds a new problem with a maintainer's packages in a repository, such as a homepage or download link that has been dead for a month or has moved to HTTPS.

Actions

Steps a workflow can run in Repology.

  • Get a projectGet a project's newest version across every repository Repology tracks, with its development version, description and licenses, how many repositories are up to date or outdated, and one row per repository with its version and status.
  • List a project's packagesList every package of a project in every repository, or only in some repositories or with some statuses, each with its package names, version as the repository writes it, status, maintainers, licenses and whether it is flagged potentially vulnerable.
  • Get a project's version in a repositoryGet the version of a project one repository has, such as curl in Debian 13, beside the newest version anywhere, and whether it is up to date or outdated. 'Found' is false when the repository doesn't package it.
  • Search projectsFind projects by part of their name, in or missing from a repository, by maintainer or category, outdated, up to date, with problems or potentially vulnerable, and by how many repositories have them, 200 a page by name. Each comes with its newest version and how many repositories are up to date.
  • List a repository's projectsList the projects a repository packages that are outdated (or up to date, potentially vulnerable, with problems, or all), 200 a page by name, each with the repository's version beside the newest. Narrow it to one maintainer for their to-do list.
  • Find a project by package nameFind the Repology project a repository's package belongs to, by the name the repository gives it, such as www/firefox in FreeBSD or firefox-esr in Debian. 'Found' is false when the repository has no package by that name.
  • List a repository's problemsList the problems Repology found with a repository's packages, or one maintainer's there: homepage and download links dead for a month, links that moved to HTTPS, and missing or unknown CPE names, 200 a page by project, each with what to do.
  • List recent changes in a repositoryList what changed in a repository over the last month, newest first, from Repology's feed: packages added or removed, updated to the newest version, or left behind by a newer one elsewhere. Narrow it to a maintainer, a project or some kinds of change.

Automate Repology with Lodol.

Connect Repology and ask your AI for your first workflow.

Free plan, no credit card