# Repology

> Track the versions of free software packaged across hundreds of Linux and BSD distributions, Homebrew, nixpkgs and language registries with Repology. Get a project's newest version and where each repository stands, check whether a repository's package is outdated, list a repository's or a maintainer's outdated packages and problems, follow recent changes, and run a workflow when a new version comes out. No account or API key required.

App · 8 actions. Web page: https://docs.lodol.com/docs/integrations/repology

## Actions

### Find a project by package name

Find 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.

**Inputs**

- Repository (`repository`, text, required): The repository the package is in.
- Package name (`package`, text, required): The package's name in that repository, as its own tools write it.
- Name type (`name_type`, text): Whether that is the source package's name (what the package is built from) or a binary package's (what is installed). Repositories with one kind of name use the source name. One of: `srcname` (Source package name), `binname` (Binary package name). Default: `srcname`.

**Outputs**

- `ambiguous` (true/false): True when the package belongs to several projects.
- `found` (true/false): True when Repology knows the package; false when the repository has no package by that name.
- `name_type` (text): 'srcname' (source package) or 'binname' (binary).
- `package` (text): The package name looked up.
- `project` (text): The project the package belongs to (the first, when there are several); empty when not found.
- `project_url` (text): The project's page on Repology, with every version.
- `projects` (list): Every project the package belongs to; more than one only when Repology splits the package, as with iperf2 and iperf3.
- `repository` (text): The repository's id on Repology, such as 'debian_13' or 'freebsd'. Every action that takes a repository accepts it.
- `repository_name` (text): The repository's name, such as 'Debian 13'.

**Example output**

```json
{
  "ambiguous": false,
  "found": true,
  "name_type": "srcname",
  "package": "ftp/curl",
  "project": "curl",
  "project_url": "https://repology.org/project/curl/versions",
  "projects": [
    "curl"
  ],
  "repository": "freebsd",
  "repository_name": "FreeBSD Ports"
}
```

### Get a project

Get 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.

**Inputs**

- Project (`project`, text, required): The project's name on Repology, in lowercase, such as firefox, curl or python:requests (language modules are prefixed with their language). A link to its Repology page works too. 'Search projects' finds it.

**Outputs**

- `categories` (list): Every category the repositories file it under, most used first.
- `devel_version` (text): The newest development version (a beta or release candidate a repository packages), when there is one.
- `licenses` (list): Every license the repositories list, most listed first.
- `newest_version` (text): The newest stable version Repology sees in any repository, such as '8.23.0'; empty when no repository's version can be compared.
- `newest_versions` (list): Every way the newest version is written, most packaged first (most projects have one).
- `outdated_repository_count` (number): How many repositories have only an older version.
- `package_count` (number): How many packages of it there are in all.
- `project` (text): The project's name on Repology, such as 'firefox' or 'python:requests'. Every action that takes a project accepts it.
- `project_url` (text): The project's page on Repology, with every version.
- `repositories` (list): One row per repository, by name: its version and status.
- `repository_count` (number): How many repositories package it.
- `status_counts` (object): How many packages have each status.
- `summary` (text): The description most repositories give.
- `up_to_date_repository_count` (number): How many repositories have the newest version.
- `vulnerable_repository_count` (number): How many repositories have a version flagged potentially vulnerable.

**Example output**

```json
{
  "categories": [
    "libs",
    "ftp"
  ],
  "devel_version": null,
  "licenses": [
    "curl"
  ],
  "newest_version": "8.23.0",
  "newest_versions": [
    "8.23.0"
  ],
  "outdated_repository_count": 1,
  "package_count": 3,
  "project": "curl",
  "project_url": "https://repology.org/project/curl/versions",
  "repositories": [
    {
      "package_count": 1,
      "repository": "arch",
      "repository_name": "Arch Linux",
      "status": "newest",
      "status_label": "Up to date",
      "up_to_date": true,
      "version": "8.23.0",
      "vulnerable": false
    },
    {
      "package_count": 1,
      "repository": "debian_13",
      "repository_name": "Debian 13",
      "status": "outdated",
      "status_label": "Outdated",
      "up_to_date": false,
      "version": "8.14.1",
      "vulnerable": true
    },
    {
      "package_count": 1,
      "repository": "freebsd",
      "repository_name": "FreeBSD Ports",
      "status": "newest",
      "status_label": "Up to date",
      "up_to_date": true,
      "version": "8.23.0",
      "vulnerable": false
    }
  ],
  "repository_count": 3,
  "status_counts": {
    "devel": 0,
    "ignored": 0,
    "incorrect": 0,
    "legacy": 0,
    "newest": 2,
    "noscheme": 0,
    "outdated": 1,
    "rolling": 0,
    "unique": 0,
    "untrusted": 0
  },
  "summary": "command line tool and library for transferring data with URLs",
  "up_to_date_repository_count": 2,
  "vulnerable_repository_count": 1
}
```

### Get a project's version in a repository

Get 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.

**Inputs**

- Project (`project`, text, required): The project's name on Repology, in lowercase, such as firefox, curl or python:requests (language modules are prefixed with their language). A link to its Repology page works too. 'Search projects' finds it.
- Repository (`repository`, text, required): The repository to look in, such as Debian 13 or Homebrew.

**Outputs**

- `found` (true/false): True when the repository packages the project.
- `newest_version` (text): The newest stable version Repology sees in any repository, such as '8.23.0'; empty when no repository's version can be compared.
- `original_version` (text): That version exactly as the repository writes it.
- `outdated` (true/false): True when the repository has only an older version.
- `package_count` (number): How many packages of it the repository has.
- `packages` (list): Every package of the project in this repository.
- `project` (text): The project's name on Repology, such as 'firefox' or 'python:requests'. Every action that takes a project accepts it.
- `project_url` (text): The project's page on Repology, with every version.
- `repository` (text): The repository's id on Repology, such as 'debian_13' or 'freebsd'. Every action that takes a repository accepts it.
- `repository_name` (text): The repository's name, such as 'Debian 13'.
- `status` (text): How the version compares with the newest anywhere: one of newest, devel, unique, outdated, legacy, rolling, noscheme, incorrect, untrusted, ignored. 'newest' is up to date, 'outdated' is behind.
- `status_label` (text): The status in words, such as 'Up to date' or 'Outdated'.
- `up_to_date` (true/false): True when the repository has the newest version.
- `version` (text): The repository's version (its best package's); empty when it doesn't package the project.

**Example output**

```json
{
  "found": true,
  "newest_version": "8.23.0",
  "original_version": "8.14.1-2+deb13u7",
  "outdated": true,
  "package_count": 1,
  "packages": [
    {
      "binary_name": "curl",
      "binary_names": [],
      "categories": [
        "libs"
      ],
      "licenses": [],
      "maintainers": [
        "team+curl@tracker.debian.org",
        "samueloph@debian.org"
      ],
      "name": "curl",
      "original_version": "8.14.1-2+deb13u7",
      "repository": "debian_13",
      "repository_name": "Debian 13",
      "source_name": "curl",
      "status": "outdated",
      "status_label": "Outdated",
      "subrepository": "trixie/main",
      "summary": null,
      "version": "8.14.1",
      "vulnerable": true
    }
  ],
  "project": "curl",
  "project_url": "https://repology.org/project/curl/versions",
  "repository": "debian_13",
  "repository_name": "Debian 13",
  "status": "outdated",
  "status_label": "Outdated",
  "up_to_date": false,
  "version": "8.14.1"
}
```

### List a project's packages

List 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.

**Inputs**

- Project (`project`, text, required): The project's name on Repology, in lowercase, such as firefox, curl or python:requests (language modules are prefixed with their language). A link to its Repology page works too. 'Search projects' finds it.
- Repositories (`repositories`, list): Only packages in these repositories. Leave empty for all.
- Statuses (`statuses`, list): Only packages with these statuses, such as Outdated. Leave empty for every status. One or more of: `newest` (Up to date), `devel` (Up to date (development version)), `unique` (Only in this repository family), `outdated`, `legacy` (Legacy (an older branch kept alongside a newer one)), `rolling` (Rolling (follows the latest code)), `noscheme` (Version without a usable scheme), `incorrect` (Incorrect version), `untrusted` (Untrusted version), `ignored` (Ignored version).
- Most packages (`limit`, number): The most packages to return, by repository name. Popular projects have thousands (Firefox has over 3,000 with its language packs). From 1 to 1000. Default: `200`.

**Outputs**

- `count` (number): How many are returned here.
- `newest_version` (text): The newest stable version Repology sees in any repository, such as '8.23.0'; empty when no repository's version can be compared.
- `packages` (list): The packages, by repository name.
- `project` (text): The project's name on Repology, such as 'firefox' or 'python:requests'. Every action that takes a project accepts it.
- `project_url` (text): The project's page on Repology, with every version.
- `total` (number): How many packages matched.
- `truncated` (true/false): True when more matched than 'Most packages' allows; narrow the repositories or statuses, or raise it.

**Example output**

```json
{
  "count": 3,
  "newest_version": "8.23.0",
  "packages": [
    {
      "binary_name": "curl",
      "binary_names": [],
      "categories": [],
      "licenses": [
        "curl"
      ],
      "maintainers": [],
      "name": "curl",
      "original_version": "8.23.0-1",
      "repository": "arch",
      "repository_name": "Arch Linux",
      "source_name": "curl",
      "status": "newest",
      "status_label": "Up to date",
      "subrepository": "core",
      "summary": "command line tool and library for transferring data with URLs",
      "version": "8.23.0",
      "vulnerable": false
    },
    {
      "binary_name": "curl",
      "binary_names": [],
      "categories": [
        "libs"
      ],
      "licenses": [],
      "maintainers": [
        "team+curl@tracker.debian.org",
        "samueloph@debian.org"
      ],
      "name": "curl",
      "original_version": "8.14.1-2+deb13u7",
      "repository": "debian_13",
      "repository_name": "Debian 13",
      "source_name": "curl",
      "status": "outdated",
      "status_label": "Outdated",
      "subrepository": "trixie/main",
      "summary": null,
      "version": "8.14.1",
      "vulnerable": true
    },
    {
      "binary_name": "curl",
      "binary_names": [],
      "categories": [
        "ftp"
      ],
      "licenses": [],
      "maintainers": [
        "sunpoet@freebsd.org"
      ],
      "name": "ftp/curl",
      "original_version": "8.23.0",
      "repository": "freebsd",
      "repository_name": "FreeBSD Ports",
      "source_name": "ftp/curl",
      "status": "newest",
      "status_label": "Up to date",
      "subrepository": null,
      "summary": "Command line tool and library for transferring data with URLs",
      "version": "8.23.0",
      "vulnerable": false
    }
  ],
  "project": "curl",
  "project_url": "https://repology.org/project/curl/versions",
  "total": 3,
  "truncated": false
}
```

### List a repository's problems

List 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.

**Inputs**

- Repository (`repository`, text, required): The repository whose problems to list.
- Maintainer (`maintainer`, text): Only packages this maintainer looks after, by the email address Repology lists them by. Leave empty for every maintainer.
- Problem types (`problem_types`, list): Only these kinds of problem, from each page. Leave empty for every kind. One or more of: `homepage_dead` (Homepage link is dead), `homepage_permanent_https_redirect` (Homepage link moved to HTTPS), `homepage_discontinued_google` (Homepage on Google Code, which has closed), `homepage_discontinued_codeplex` (Homepage on CodePlex, which has closed), `homepage_discontinued_gna` (Homepage on Gna, which has closed), `homepage_discontinued_cpan` (Homepage on search.cpan.org, which has closed), `homepage_sourceforge_missing_trailing_slash` (SourceForge homepage link needs a trailing slash), `download_dead` (Download link is dead), `download_permanent_https_redirect` (Download link moved to HTTPS), `cpe_unreferenced` (CPE name not known to the NVD), `cpe_missing` (CPE name missing).
- After project (`after`, text): For the next page: the 'next_after' of the page before. Leave empty for the first page.

**Outputs**

- `count` (number): How many problems are on this page.
- `maintainer` (text): The maintainer whose problems these are; empty for the whole repository.
- `more` (true/false): True when Repology has more after this page; put 'next_after' in 'After project' to get them.
- `next_after` (text): The name to put in 'After project' for the next page; empty on the last.
- `problems` (list): The problems, by project name.
- `repository` (text): The repository's id on Repology, such as 'debian_13' or 'freebsd'. Every action that takes a repository accepts it.
- `repository_name` (text): The repository's name, such as 'Debian 13'.

**Example output**

```json
{
  "count": 2,
  "maintainer": "ports@freebsd.org",
  "more": false,
  "next_after": null,
  "problems": [
    {
      "binary_name": "zangband",
      "cpe": null,
      "description": "Homepage link http://www.zangband.org/ has been dead (HTTP 404) for more than a month.",
      "link_status": "HTTP 404",
      "maintainer": "ports@freebsd.org",
      "original_version": "2.7.5.p1",
      "project": "zangband",
      "project_url": "https://repology.org/project/zangband/versions",
      "repository": "freebsd",
      "source_name": "games/zangband",
      "target": null,
      "type": "homepage_dead",
      "type_label": "Homepage link is dead",
      "url": "http://www.zangband.org/",
      "version": "2.7.5.p1"
    },
    {
      "binary_name": "ztoolkit",
      "cpe": null,
      "description": "Homepage link http://www.ztoolkit.org/ permanently redirects to https://www.ztoolkit.org/; use that.",
      "link_status": null,
      "maintainer": "ports@freebsd.org",
      "original_version": "0.1_8",
      "project": "ztoolkit",
      "project_url": "https://repology.org/project/ztoolkit/versions",
      "repository": "freebsd",
      "source_name": "graphics/ztoolkit",
      "target": "https://www.ztoolkit.org/",
      "type": "homepage_permanent_https_redirect",
      "type_label": "Homepage link moved to HTTPS",
      "url": "http://www.ztoolkit.org/",
      "version": "0.1"
    }
  ],
  "repository": "freebsd",
  "repository_name": "FreeBSD Ports"
}
```

### List a repository's projects

List 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.

**Inputs**

- Repository (`repository`, text, required): The repository to list, such as FreeBSD Ports or AUR.
- Which projects (`which`, text): Outdated ones by default: where the repository's version is behind the newest. One of: `outdated`, `newest` (Up to date), `vulnerable` (Potentially vulnerable), `problematic` (With problems), `all` (Every project). Default: `outdated`.
- Maintainer (`maintainer`, text): Only packages this maintainer looks after, by the email address Repology lists them by. Leave empty for every maintainer.
- Name contains (`search`, text): Only projects whose name contains this, such as ssl or python:.
- After project (`after`, text): For the next page: the 'next_after' of the page before. Leave empty for the first page.

**Outputs**

- `count` (number): How many projects are on this page.
- `more` (true/false): True when Repology has more after this page; put 'next_after' in 'After project' to get them.
- `next_after` (text): The name to put in 'After project' for the next page; empty on the last.
- `projects` (list): The projects, by name, up to 200 a page, each with the repository's version beside the newest.
- `repository` (text): The repository's id on Repology, such as 'debian_13' or 'freebsd'. Every action that takes a repository accepts it.
- `repository_name` (text): The repository's name, such as 'Debian 13'.
- `which` (text): Which projects were listed: outdated, newest, vulnerable, problematic or all.

**Example output**

```json
{
  "count": 2,
  "more": false,
  "next_after": null,
  "projects": [
    {
      "binary_name": "curl",
      "maintainers": [
        "sunpoet@freebsd.org"
      ],
      "name": "ftp/curl",
      "newest_version": "8.23.0",
      "original_version": "8.23.0",
      "outdated": false,
      "package_count": 1,
      "project": "curl",
      "project_url": "https://repology.org/project/curl/versions",
      "source_name": "ftp/curl",
      "status": "newest",
      "status_label": "Up to date",
      "version": "8.23.0",
      "vulnerable": false
    },
    {
      "binary_name": "curlie",
      "maintainers": [
        "yuri@freebsd.org"
      ],
      "name": "ftp/curlie",
      "newest_version": "1.8.2",
      "original_version": "1.7.2_29",
      "outdated": true,
      "package_count": 1,
      "project": "curlie",
      "project_url": "https://repology.org/project/curlie/versions",
      "source_name": "ftp/curlie",
      "status": "outdated",
      "status_label": "Outdated",
      "version": "1.7.2",
      "vulnerable": false
    }
  ],
  "repository": "freebsd",
  "repository_name": "FreeBSD Ports",
  "which": "all"
}
```

### List recent changes in a repository

List 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.

**Inputs**

- Repository (`repository`, text, required): The repository whose changes to list.
- Maintainer (`maintainer`, text): Only this maintainer's packages, by the email address Repology lists them by. Leave empty for the whole repository.
- Kinds of change (`change_types`, list): Only these kinds of change. Leave empty for every kind. One or more of: `outdated` (Became outdated), `uptodate` (Up to date), `added`, `removed`, `ignored` (Ignored version).
- Project (`project`, text): Only changes to this project, such as curl. Leave empty for every project.
- Most changes (`limit`, number): The most changes to return, newest first. Repology keeps the last 500, or a month's. From 1 to 500. Default: `100`.

**Outputs**

- `changes` (list): The changes, newest first.
- `count` (number): How many are returned here.
- `maintainer` (text): The maintainer whose packages these are; empty for the whole repository.
- `repository` (text): The repository's id on Repology, such as 'debian_13' or 'freebsd'. Every action that takes a repository accepts it.
- `repository_name` (text): The repository's name, such as 'Debian 13'.
- `total` (number): How many recent changes matched.

**Example output**

```json
{
  "changes": [
    {
      "id": 32076436,
      "newest_versions": [
        "26.9.9.28"
      ],
      "project": "clickhouse",
      "project_url": "https://repology.org/project/clickhouse/versions",
      "repository": "freebsd",
      "time": "2026-10-24T00:47:30+00:00",
      "title": "clickhouse 26.8.3.105 is outdated by 26.9.9.28",
      "type": "outdated",
      "type_label": "Became outdated",
      "version": "26.8.3.105"
    },
    {
      "id": 32076274,
      "newest_versions": [],
      "project": "brotli",
      "project_url": "https://repology.org/project/brotli/versions",
      "repository": "freebsd",
      "time": "2026-10-24T00:47:29+00:00",
      "title": "brotli 1.2.1 is up to date",
      "type": "uptodate",
      "type_label": "Up to date",
      "version": "1.2.1"
    },
    {
      "id": 32064627,
      "newest_versions": [],
      "project": "ruby:rbs-gitlab",
      "project_url": "https://repology.org/project/ruby%3Arbs-gitlab/versions",
      "repository": "freebsd",
      "time": "2026-10-23T17:50:17+00:00",
      "title": "ruby:rbs-gitlab is now tracked",
      "type": "added",
      "type_label": "Added",
      "version": null
    }
  ],
  "count": 3,
  "maintainer": null,
  "repository": "freebsd",
  "repository_name": "FreeBSD Ports",
  "total": 3
}
```

### Search projects

Find 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.

**Inputs**

- Name contains (`search`, text): Only projects whose name contains this, such as ssl or python:.
- In repository (`in_repository`, text): Only projects this repository packages. The 'Only projects' choices then apply to its packages.
- Not in repository (`not_in_repository`, text): Only projects this repository doesn't package, such as candidates to add to it.
- Maintainer (`maintainer`, text): Only packages this maintainer looks after, by the email address Repology lists them by. Leave empty for every maintainer.
- Category (`category`, text): Only projects some repository files under this category, such as games or devel. Repositories name their categories differently.
- Only projects (`only`, list): Only projects that are all of these somewhere (or in 'In repository', when set). Leave empty for every project. One or more of: `outdated` (Outdated somewhere), `newest` (Up to date somewhere), `problematic` (With problems), `vulnerable` (Potentially vulnerable).
- In at least this many repositories (`min_repositories`, number): Only projects at least this many repositories package. From 0 to 1000.
- In at most this many repositories (`max_repositories`, number): Only projects at most this many repositories package. From 0 to 1000.
- In at least this many families (`min_families`, number): Only projects in at least this many families. A family is one distribution's repositories together, such as every Debian release. From 0 to 1000.
- In at most this many families (`max_families`, number): Only projects in at most this many families; 1 finds those only one distribution packages. From 0 to 1000.
- Up to date in at least this many families (`min_families_up_to_date`, number): Only projects at least this many families have the newest version of. From 0 to 1000.
- Up to date in at most this many families (`max_families_up_to_date`, number): Only projects at most this many families have the newest version of. From 0 to 1000.
- After project (`after`, text): For the next page: the 'next_after' of the page before. Leave empty for the first page.

**Outputs**

- `count` (number): How many projects are on this page.
- `more` (true/false): True when Repology has more after this page; put 'next_after' in 'After project' to get them.
- `next_after` (text): The name to put in 'After project' for the next page; empty on the last.
- `projects` (list): The projects, by name, up to 200 a page.

**Example output**

```json
{
  "count": 2,
  "more": false,
  "next_after": null,
  "projects": [
    {
      "devel_version": null,
      "newest_version": "8.23.0",
      "outdated_repository_count": 1,
      "package_count": 3,
      "project": "curl",
      "project_url": "https://repology.org/project/curl/versions",
      "repository_count": 3,
      "summary": "command line tool and library for transferring data with URLs",
      "up_to_date_repository_count": 2,
      "vulnerable": true
    },
    {
      "devel_version": null,
      "newest_version": "1.8.2",
      "outdated_repository_count": 1,
      "package_count": 2,
      "project": "curlie",
      "project_url": "https://repology.org/project/curlie/versions",
      "repository_count": 2,
      "summary": "Frontend to curl that adds the ease of use of httpie",
      "up_to_date_repository_count": 1,
      "vulnerable": false
    }
  ]
}
```
