Search results

Add entries to the documentation for advanced and flexible parsing of VERS

Status: Open.

#69 In package-url/vers-spec;

· pombredanne opened on May 13, 2026

Issues in vers-test.schema-0.1.json

Status: Open.

#68 In package-url/vers-spec;

· peinjoh opened on May 12, 2026

Semantic preservation requirements for encode/decode in the presence of pre-release semantics

Status: Open.

#57 In package-url/vers-spec;

· maennchen opened on Feb 18, 2026

Version containment algorithm is incorrect in case of single inequality

Status: Open.

#54 In package-url/vers-spec;

· manueljacob opened on Jan 19, 2026

URL quoting specification issue

Status: Open.

#52 In package-url/vers-spec;

· milux opened on Nov 26, 2025

Clarify usage of << and >>

Status: Open.

#51 In package-url/vers-spec;

· tschmidtb51 opened on Nov 25, 2025

Allow only canonical vers

Status: Open.

#50 In package-url/vers-spec;

· tschmidtb51 opened on Nov 25, 2025

Clarify vers representation of Elixir ~> range with pre-release semantics

Status: Open.

#49 In package-url/vers-spec;

· maennchen opened on Nov 24, 2025

Complete JSON Schema 1.0 for VERS tests

Status: Open.

#47 In package-url/vers-spec;

· mjherzog opened on Oct 29, 2025

Create JSON Schema for VERS types

Status: Open.

#46 In package-url/vers-spec;

· mjherzog opened on Oct 29, 2025

·  

VERS ECMA Standard 1st Edition

Include new vers library tests in test suite

Status: Open.

#21 In package-url/vers-spec;

· pombredanne opened on Jul 29, 2025

Do pkg and vers URIs need a third scheme? The case for "lib" URIs

Status: Open.

#23 In package-url/vers-spec;

· sjn opened on Dec 6, 2024