vers 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: ae79cd7ee206fc3d6a786291f57f0c3fd55c37cb0db864c2eba049cfb820542c
+  data.tar.gz: dc8b996bcc1aad44e585eab361dc396bcd0b5b864d9cc287553c55c036bcbe01
+SHA512:
+  metadata.gz: 1d9c6b0983644a8f52807a6dfa6d524f447c1856273bf6e86810c4c4f52767ebdd3c26bd77bc6ebff378f5147292b49d4636e9baed0576e1a1f2851dcd32248c
+  data.tar.gz: 0e7b47362f4f5ce6395d1785f92dcb21b71e737287d59547c95b11d0ed1b8c5979f5c80379df4a437c875d908639f72a2ce2a89ed4f74106faab5fffa4bab80f

data/CHANGELOG.md

@@ -0,0 +1,87 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [1.0.0] - 2025-01-25
+
+### Added
+- **JSON Test Dataset** (`test-suite-data.json`) with 37 comprehensive test cases for cross-language compatibility
+- **Enhanced NPM Support**: X-ranges (`1.2.x`), OR logic (`||`), wildcard support, invalid range validation
+- **Maven Union Ranges**: Complex multi-range support like `"[2.0,2.3.1] , [2.4.0,2.12.2) , [2.13.0,2.15.0)"`
+- **Prerelease Version Handling**: Caret and hyphen ranges with prerelease versions
+- **Specification Compliance Tests**: Automated test suite validating VERS spec compliance
+- **Cross-Ecosystem Compatibility Tests**: Verify equivalent ranges work across package managers
+- **Bidirectional Conversion Tests**: Ensure parsing and regenerating produces equivalent results
+- **Enhanced Rake Tasks**: 
+  - `rake spec:compliance` - Run VERS specification compliance test suite
+  - `rake spec:test_data` - Show JSON test dataset information
+- **Comprehensive Error Handling**: Invalid ranges like `"blerg"` and `"git+https://..."` raise proper errors
+- **Maven Malformed Range Validation**: Detect and reject invalid bracket notation like `"(1.0.0]"`
+
+### Enhanced
+- **NPM Parser**: Added support for empty ranges, X-ranges, OR logic, and invalid range detection
+- **Maven Parser**: Fixed union range parsing with proper bracket preservation
+- **Test Coverage**: Expanded from 113 to 129 tests with 725 assertions, all passing
+- **Documentation**: Added package manager syntax comparison table inspired by Eve Martin-Jones and Elitsa Bankova's presentation
+
+## [0.1.0] - 2025-01-25
+
+### Added
+
+- **Initial release** of Vers Ruby gem for parsing, comparing and sorting versions according to the VERS specification
+- **Mathematical interval model** for precise version range representation
+- **Universal version range parsing** with support for 6 package ecosystems:
+  - npm (Node.js): Caret ranges (^1.2.3), tilde ranges (~1.2.3), hyphen ranges (1.2.3 - 2.3.4)
+  - gem (RubyGems): Pessimistic operator (~> 1.2), standard operators (>=, <=, etc.)
+  - pypi (Python): Comma-separated constraints (>=1.0,<2.0), exclusions (!=1.5.0)
+  - maven (Java): Bracket notation ([1.0,2.0], (1.0,2.0), [1.0,2.0))
+  - debian: Standard comparison operators (>=1.0.0, <<2.0.0)
+  - rpm: Standard comparison operators (>=1.0.0, <=2.0.0)
+- **VERS URI format support** - parse and generate vers URI strings (e.g., `vers:npm/>=1.2.3|<2.0.0`)
+- **Bidirectional conversion** between native package manager syntax and universal vers URI format
+- **Set operations** on version ranges:
+  - Union: combine multiple version ranges
+  - Intersection: find overlapping versions
+  - Complement: find versions NOT in a range
+  - Exclusion: remove specific versions from ranges
+- **Semantic versioning features** inspired by the semantic gem:
+  - Version increment methods (`increment_major`, `increment_minor`, `increment_patch`)
+  - Pessimistic constraint checking (`version.satisfies?("~> 1.2")`)
+  - Prerelease and build metadata support
+  - Version comparison and normalization
+- **Comprehensive error handling** with detailed parsing exceptions
+- **Core classes**:
+  - `Vers::Version` - semantic version parsing and comparison
+  - `Vers::Interval` - mathematical interval representation with bounds
+  - `Vers::VersionRange` - collection of intervals with set operations
+  - `Vers::Constraint` - individual version constraints (>=, <, etc.)
+  - `Vers::Parser` - extensible translation layer for package manager syntaxes
+- **Complete test coverage** with 113 tests and 366 assertions
+- **Comprehensive RDoc documentation** for all public APIs
+- **Development tooling**:
+  - Rake tasks for specification validation and examples
+  - Security policy and contributing guidelines
+  - GitHub Actions-ready project structure
+
+### Documentation
+
+- **README.md** with comprehensive usage examples and API documentation
+- **CONTRIBUTING.md** with development guidelines and project structure
+- **SECURITY.md** with vulnerability reporting procedures
+- **VERSION-RANGE-SPEC.rst** - official VERS specification included in repository
+- **RDoc documentation** for all classes and methods
+
+### Dependencies
+
+- **Ruby 3.2+** required
+- **No runtime dependencies** - pure Ruby implementation
+- **Minitest** for testing (development dependency only)
+
+[Unreleased]: https://github.com/andrew/vers/compare/v1.0.0...HEAD
+[1.0.0]: https://github.com/andrew/vers/compare/v0.1.0...v1.0.0
+[0.1.0]: https://github.com/andrew/vers/releases/tag/v0.1.0

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

data/CONTRIBUTING.md

@@ -0,0 +1,194 @@
+# Contributing to Vers
+
+Thank you for your interest in contributing to the Vers Ruby library! This document provides guidelines and information for contributors.
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by our [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
+
+## How to Contribute
+
+### Reporting Issues
+
+Before creating an issue, please:
+1. Search existing issues to avoid duplicates
+2. Use the latest version of the gem
+3. Provide a clear, descriptive title
+4. Include steps to reproduce the issue
+5. Share relevant code examples or error messages
+
+### Suggesting Enhancements
+
+Enhancement suggestions are welcome! Please:
+1. Check if the enhancement is already requested
+2. Explain the use case and expected behavior
+3. Consider if it fits the project's scope
+4. Be willing to help implement if accepted
+
+### Pull Requests
+
+1. **Fork** the repository
+2. **Create** a feature branch (`git checkout -b my-new-feature`)
+3. **Make** your changes following our coding standards
+4. **Add** tests for your changes
+5. **Ensure** all tests pass (`rake test`)
+6. **Run** the full test suite including any compliance tests
+7. **Commit** your changes with clear, descriptive messages
+8. **Push** to your branch (`git push origin my-new-feature`)
+9. **Create** a Pull Request with a clear description
+
+## Development Setup
+
+### Prerequisites
+
+- Ruby 3.2 or higher
+- Bundler gem
+
+### Setup
+
+```bash
+git clone https://github.com/andrew/vers.git
+cd vers
+bundle install
+```
+
+### Running Tests
+
+```bash
+# Run all tests
+rake test
+
+# Run tests with coverage
+bundle exec rake test
+
+# Show all available tasks
+rake -T
+```
+
+### Coding Standards
+
+- Follow Ruby best practices and conventions
+- Use meaningful variable and method names
+- Add RDoc documentation for public methods
+- Keep methods focused and concise
+- Follow the existing code style
+- Use `frozen_string_literal: true` at the top of all files
+
+### Testing Requirements
+
+All contributions must include appropriate tests:
+
+- **Unit tests** for new functionality
+- **Integration tests** for feature interactions
+- **Edge case tests** for boundary conditions
+- **Error handling tests** for exception cases
+
+### Documentation
+
+- Update the README.md if adding new features
+- Add RDoc documentation for complex methods
+- Update CHANGELOG.md following the format
+- Include examples in documentation
+
+## Project Structure
+
+```
+├── lib/
+│   ├── vers.rb                 # Main module
+│   └── vers/
+│       ├── version.rb          # Version class with semantic versioning
+│       ├── interval.rb         # Mathematical interval model
+│       ├── version_range.rb    # Version range operations
+│       ├── constraint.rb       # Individual version constraints
+│       └── parser.rb           # Package manager syntax parsers
+├── test/                       # Test files
+├── VERSION-RANGE-SPEC.rst     # Official specification
+└── README.md                  # Project documentation
+```
+
+## Adding New Package Manager Support
+
+To add support for a new package manager:
+
+1. **Add parser methods** to `lib/vers/parser.rb`
+2. **Include examples** in documentation
+3. **Add comprehensive tests** for the new syntax
+4. **Update README** with supported syntax examples
+5. **Verify** against VERS specification compliance
+
+## Version Range Operations
+
+When working with version ranges:
+
+1. **Use interval model** for internal representation
+2. **Test set operations** (union, intersection, complement)
+3. **Verify mathematical correctness** of operations
+4. **Handle edge cases** like empty and unbounded ranges
+
+## VERS Specification Compliance
+
+This library maintains compliance with the VERS specification:
+
+- All changes must maintain specification compliance
+- New features should align with the spec
+- Report spec issues upstream when discovered
+- Test against official specification examples
+
+## Release Process
+
+Releases are handled by maintainers:
+
+1. Update version in `lib/vers/version.rb`
+2. Update `CHANGELOG.md` with changes
+3. Run full test suite
+4. Create release tag
+5. Publish to RubyGems
+
+## Getting Help
+
+- **Issues**: Use GitHub issues for bugs and feature requests
+- **Discussions**: Use GitHub discussions for questions
+- **Security**: Follow our [Security Policy](SECURITY.md)
+
+## Recognition
+
+Contributors will be recognized in:
+- Git commit history
+- CHANGELOG.md for significant contributions
+- Project documentation where appropriate
+
+## License
+
+By contributing to Vers, you agree that your contributions will be licensed under the [MIT License](LICENSE).
+
+## Development Philosophy
+
+### Mathematical Accuracy
+
+Version ranges are implemented using mathematical interval theory:
+- Intervals have clear bounds and inclusivity rules
+- Set operations follow mathematical principles
+- Edge cases are handled consistently
+
+### Extensibility
+
+The architecture supports easy extension:
+- New package managers can be added via parser methods
+- Version comparison logic is centralized
+- Testing framework supports new syntax validation
+
+### Performance
+
+Consider performance implications:
+- Avoid excessive regular expression backtracking
+- Cache compiled patterns where appropriate
+- Test with large version lists
+
+### Error Handling
+
+Provide clear, actionable error messages:
+- Include context about what failed
+- Suggest corrections when possible
+- Use specific exception types
+
+Thank you for contributing to make Vers better for everyone!

data/README.md

@@ -0,0 +1,257 @@
+# Vers - Version Range Parser for Ruby
+
+A Ruby library for parsing, comparing and sorting versions according to the [VERS specification](https://github.com/package-url/purl-spec/blob/main/VERSION-RANGE-SPEC.rst).
+
+This gem provides tools for working with version ranges across different package managers, using a mathematical interval model internally and supporting the vers specification from the Package URL (PURL) project.
+
+[![Ruby](https://img.shields.io/badge/ruby-%3E%3D%203.2-red.svg)](https://www.ruby-lang.org/)
+[![Gem Version](https://badge.fury.io/rb/vers.svg)](https://rubygems.org/gems/vers)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+
+**[Available on RubyGems](https://rubygems.org/gems/vers)** | **[API Documentation](https://rdoc.info/github/andrew/vers)** | **[GitHub Repository](https://github.com/andrew/vers)**
+
+## Features
+
+- **Universal version range parsing** with support for 6 package ecosystems (npm, gem, pypi, maven, debian, rpm)
+- **Mathematical interval model** for precise set operations (union, intersection, complement)
+- **VERS specification compliance** with full support for the Package URL version range specification
+- **Native syntax support** - parse native package manager syntax (^1.2.3, ~>1.0, >=1.0,<2.0, [1.0,2.0))
+- **Bidirectional conversion** between native syntax and universal vers URI format
+- **Semantic versioning features** - version increment, constraint checking, prerelease handling
+- **Comprehensive error handling** with detailed parsing exceptions
+- **100% test coverage** with 113 tests and 366 assertions
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'vers'
+```
+
+And then execute:
+
+```bash
+bundle install
+```
+
+Or install it yourself as:
+
+```bash
+gem install vers
+```
+
+## Quick Start
+
+```ruby
+require 'vers'
+
+# Parse a vers URI
+range = Vers.parse("vers:npm/>=1.2.3|<2.0.0")
+range.contains?("1.5.0")  # => true
+range.contains?("2.1.0")  # => false
+
+# Parse native package manager syntax
+npm_range = Vers.parse_native("^1.2.3", "npm")
+gem_range = Vers.parse_native("~> 1.0", "gem")
+
+# Check version containment
+Vers.satisfies?("1.5.0", ">=1.0.0,<2.0.0")  # => true
+
+# Compare versions
+Vers.compare("1.2.3", "1.2.4")  # => -1
+
+# Version operations
+version = Vers::Version.new("1.2.3")
+version.increment_major  # => #<Vers::Version "2.0.0">
+version.satisfies?("~> 1.2")  # => true
+```
+
+## Supported Package Managers
+
+- **npm**: Caret ranges (^1.2.3), tilde ranges (~1.2.3), hyphen ranges (1.2.3 - 2.3.4)
+- **RubyGems**: Pessimistic operator (~> 1.2), standard operators (>=, <=, etc.)
+- **PyPI**: Comma-separated constraints (>=1.0,<2.0)
+- **Maven**: Bracket notation ([1.0,2.0], (1.0,2.0))
+- **Debian/RPM**: Standard comparison operators
+
+## Mathematical Model
+
+Internally, all version ranges are represented as mathematical intervals, similar to those used in mathematics:
+
+- `[1.0.0, 2.0.0)` represents versions from 1.0.0 (inclusive) to 2.0.0 (exclusive)
+- `(1.0.0, 2.0.0]` represents versions from 1.0.0 (exclusive) to 2.0.0 (inclusive)
+
+This allows for precise set operations like union, intersection, and complement, regardless of the original package manager syntax.
+
+## Usage Examples
+
+### Basic Version Range Parsing
+
+```ruby
+require 'vers'
+
+# Parse vers URI format
+range = Vers.parse("vers:npm/>=1.2.3|<2.0.0")
+puts range.contains?("1.5.0")  # => true
+puts range.contains?("2.1.0")  # => false
+
+# Parse native package manager syntax
+npm_range = Vers.parse_native("^1.2.3", "npm")
+gem_range = Vers.parse_native("~> 1.0", "gem")
+pypi_range = Vers.parse_native(">=1.0,<2.0", "pypi")
+maven_range = Vers.parse_native("[1.0,2.0)", "maven")
+```
+
+### Creating Version Ranges
+
+```ruby
+# Create exact version range
+exact = Vers.exact("1.2.3")
+puts exact.contains?("1.2.3")  # => true
+puts exact.contains?("1.2.4")  # => false
+
+# Create comparison ranges
+greater = Vers.greater_than("1.0.0", inclusive: true)
+less = Vers.less_than("2.0.0", inclusive: false)
+
+# Create unbounded and empty ranges
+all_versions = Vers.unbounded
+no_versions = Vers.empty
+```
+
+### Converting Between Formats
+
+```ruby
+# Parse native syntax and convert to vers URI
+npm_range = Vers.parse_native("^1.2.3", "npm")
+vers_string = Vers.to_vers_string(npm_range, "npm")
+puts vers_string  # => "vers:npm/>=1.2.3|<2.0.0"
+
+# Parse vers URI and use in your application
+range = Vers.parse("vers:gem/~>1.0")
+puts range.contains?("1.5.0")  # => true
+```
+
+### Set Operations on Version Ranges
+
+```ruby
+range1 = Vers.parse("vers:npm/>=1.0.0|<2.0.0")
+range2 = Vers.parse("vers:npm/>=1.5.0|<3.0.0")
+
+# Union: versions in either range
+union = range1.union(range2)
+puts union.contains?("0.9.0")  # => false
+puts union.contains?("1.2.0")  # => true
+puts union.contains?("2.5.0")  # => true
+
+# Intersection: versions in both ranges
+intersection = range1.intersect(range2)
+puts intersection.contains?("1.2.0")  # => false
+puts intersection.contains?("1.7.0")  # => true
+puts intersection.contains?("2.5.0")  # => false
+
+# Complement: versions NOT in range
+complement = range1.complement
+puts complement.contains?("0.5.0")  # => true
+puts complement.contains?("1.5.0")  # => false
+
+# Exclusions: remove specific versions
+excluded = range1.exclude("1.5.0")
+puts excluded.contains?("1.4.0")  # => true
+puts excluded.contains?("1.5.0")  # => false
+puts excluded.contains?("1.6.0")  # => true
+```
+
+### Version Comparison and Manipulation
+
+```ruby
+version = Vers::Version.new("1.2.3-alpha.1+build.123")
+
+# Access version components
+puts version.major      # => 1
+puts version.minor      # => 2
+puts version.patch      # => 3
+puts version.prerelease # => "alpha.1"
+puts version.build      # => "build.123"
+
+# Compare versions
+puts Vers.compare("1.2.3", "1.2.4")  # => -1
+puts Vers.compare("2.0.0", "1.9.9")  # => 1
+puts Vers.compare("1.0.0", "1.0.0")  # => 0
+
+# Increment versions (returns new Version objects)
+puts version.increment_major  # => #<Vers::Version "2.0.0">
+puts version.increment_minor  # => #<Vers::Version "1.3.0">  
+puts version.increment_patch  # => #<Vers::Version "1.2.4">
+
+# Version properties
+puts version.stable?      # => false (has prerelease)
+puts version.prerelease?  # => true
+puts version.to_h         # => {major: 1, minor: 2, patch: 3, ...}
+```
+
+### Constraint Checking
+
+```ruby
+version = Vers::Version.new("1.2.5")
+
+# Pessimistic constraint checking (Ruby-style)
+puts version.satisfies?("~> 1.2")    # => true  (>= 1.2.0, < 1.3.0)
+puts version.satisfies?("~> 1.2.3")  # => true  (>= 1.2.3, < 1.3.0)
+puts version.satisfies?("~> 1.3")    # => false
+
+# General satisfaction checking
+puts Vers.satisfies?("1.5.0", "vers:npm/>=1.0.0|<2.0.0")  # => true
+puts Vers.satisfies?("1.5.0", "^1.2.3", "npm")            # => true
+```
+
+## Specification Compliance
+
+This gem implements the [PURL Version Range Specification](https://github.com/package-url/purl-spec/blob/main/VERSION-RANGE-SPEC.rst), providing a universal way to express version ranges across different software packaging ecosystems.
+
+Learn more about the motivation and design behind VERS in the [presentation from Open Source Summit NA 2025](https://www.youtube.com/watch?v=EU-TodN27rM) ([slides PDF](https://static.sched.com/hosted_files/ossna2025/74/We%20need%20a%20standard%20for%20open%20source%20package%20requirements.pdf)) by Eve Martin-Jones and Elitsa Bankova. The following table from their talk shows how different package managers express the same version constraints:
+
+| Operator | NPM | Cargo | Carthage | RubyGems | PyPI | Maven | NuGet |
+|----------|-----|-------|----------|----------|------|-------|--------|
+| **behavior with no op** | 1.0.0 | ^1.0.0⁴ | illegal | 1.0.0 | illegal | *⁵ | >=1.0 |
+| **= ==** | =1.0 | = | == | = | == | [1.0]⁵ | [1.0]⁸ |
+| **>** | > | > | | > | > | (1.0,) | (1.0,) |
+| **>=** | >= | >= | >= | >= | >= | 1.0⁵ | 1.0⁷ᵇᵃ |
+| **<** | < | < | | < | < | (,1.0) | (,1.0) |
+| **<=** | <= | <= | | <= | <= | (,1.0] | (,1.0] |
+| **!=** | | | | != | != | | |
+| **^** | ^ | ^² | | | | | |
+| **~** | ~, ~>¹ | ~ | | | ~= | | |
+| **~>** | ¹ | | ~> | ~> | | | |
+| **wildcards** | * x X | * x X | | | * | * | |
+| **OR** | \|\| | | | | | , | |
+| **AND** | space | , | | ,³ | , | | |
+| **RANGE** | - | | | | | [,],(,)⁶ | [,],(,) |
+
+This complexity across ecosystems is exactly why VERS provides a universal format that works consistently across all package managers.
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/andrew/vers. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/andrew/vers/blob/main/CODE_OF_CONDUCT.md).
+
+## Related Projects
+
+- [purl](https://github.com/andrew/purl) - Ruby implementation of Package URL (PURL)
+- [semantic_range](https://github.com/librariesio/semantic_range) - Semantic version parsing (JavaScript style)
+- [univers](https://github.com/package-url/univers) - Python implementation of version ranges
+- [versatile](https://github.com/package-url/versatile) - Java implementation of version ranges
+
+## License
+
+The gem is available as open source under the terms of the MIT License.
+
+## Code of Conduct
+
+Everyone interacting in the Vers project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/andrew/vers/blob/main/CODE_OF_CONDUCT.md).