Versions Packages Information History Related Badges Report

Report problem for perl:encode-compat

While repology tries its best in matching packages across different repositories, this is quite a complex task:

Repology uses a set of manually edited rules to resolve these cases. You may submit a change to the ruleset directly or use this form to suggest an improvement to the ruleset. Please only use this for problems which may be fixed by the ruleset (which are basically problems listed above).

New report

Check if the latest version detected for this project is incorrect (e.g. a non-existing version, version with incorrect format, version with date or a git commit hash) and should be ignored. Please provide a prooflink for unapparent cases (e.g. a list of VCS tags or official site mentioning actual latest version).


  • If upstream does not tag/publish official releases, please submit an issue asking them to do so first.

Check if this entry refers to multiple unrelated projects and thus needs to be split into multiple entries. Naming suggestions for new projects are welcome.

Will not split:

  • Legacy or ESR branches of the same project.
  • *-unclassified projects which lack valid homepage information.

Check if there are other Repology entries for the same project under different names which should be merged into one. Please list them in the comment field, as well as suggested target name.

Will not merge:

  • Modules (e.g. python) without consistent prefix (such as python- or python3-) (common problem for Slackbuilds and Debian source packages).
  • go:* packages, which have no official naming scheme.
  • Packages with incorrect names (should be renamed in repositories instead).
  • Lots of package variants (common for AUR and Nix) - repositories are expected to provide master project name for these.

Check if there are known older CVEs (vulnerabilities) for this project. Note that there's expected lag of CVE information propagation so there's no need to report very recent CVEs. The idea is to fill missing CPE bindings which allow matching both past and future vulnerabilities to projects.

Will not accept:

  • Reports for recent CVEs which have not been analyzed by NVD yet (so please check NVD first).
  • Reports for incorrect version ranges - please report these to NVD.