Search results

URL quoting specification issue

Status: Open.

#52 In package-url/vers-spec;

· milux opened on Nov 26, 2025

Clarify usage of <code>&lt;&lt;</code> and <code>&gt;&gt;</code>

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 <code>~&gt;</code> 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 schemes

Status: Open.

#46 In package-url/vers-spec;

· mjherzog opened on Oct 29, 2025

Update "Implementations" section of VERSION-RANGE-SPEC.md

Status: Open.

#40 In package-url/vers-spec;

· johnmhoran opened on Sep 19, 2025

Include new vers library tests in test suite

Status: Open.

#21 In package-url/vers-spec;

· pombredanne opened on Jul 29, 2025

Deconstruct VERSION-SPEC-RANGE.md into multiple topic-based markdown files

Status: Open.

#5 In package-url/vers-spec;

· mjherzog opened on Jul 29, 2025

Update vers-spec root files copied from purl-spec

Status: Open.

#3 In package-url/vers-spec;

· mjherzog opened on Jul 28, 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

There is a flaw in the VERSION-RANGE-SPEC

PURL/univers version scheme

Status: Open.

#20 In package-url/vers-spec;

· pstray opened on Dec 4, 2024