Skip to content

Upstream harvested conformance data to package-url/vers-spec #54

Description

@andrew

The upstream package-url/vers-spec conformance suite is thin (491 npm native-parse cases but 1 npm containment case, 0 maven native-parse cases, 1 gem case total, nothing for cargo/composer/pub/deb/rpm/go/hex). testdata/local/tests/ now has 34 harvested files covering those gaps, generated by tools/harvest/ from each ecosystem's reference implementation with provenance recorded in testdata/local/provenance.json.

Open a PR to package-url/vers-spec contributing the generated JSON and linking the harvester. The files already match the upstream schema (the local runner accepts both input_scheme/input_type per the 0.2 rename).

Split from #36.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions