
Reference implementation. Sync and async validators, TypeScript type inference.
LIVR is a specification, so you need an implementation for your language. All of them use the same rules format and return the same error codes. The latest version of the specification is 2.5: it adds rules to 2.0, the previous one, so an implementation of LIVR 2.0 has every rule except the new ones. The version before 2.0 was 0.4.

livrv2.13.3Reference implementation. Sync and async validators, TypeScript type inference.

Validator::LIVRv2.22
Formerly Perl 6.


validator/livr
io.github.vlbaluk:validator-livrv2.0.2Returns the standard error codes, but wraps each one together with the invalid value: {"code": "REQUIRED", "fieldValue": …}.

github.com/k33nice/go-livrv2.0.0



liverv1.1.0

Package versions and repository activity are refreshed every time the site is built.
Every implementation is checked against the shared test suite. Every week, and whenever the specification changes, CI installs each implementation the way a user would and runs all test cases against it. The score is for the LIVR 2.0 suite; the "2.5" columns show the separate suite of the rules added in LIVR 2.5: its validation cases and its schema error cases.
| Implementation | Tested version | Passed | 2.5 | 2.5 schema errors | Details |
|---|---|---|---|---|---|
| JavaScript | 2.13.3 | 70 / 70 | 84 / 84 | 179 / 179 | All cases pass |
| Perl | 2.22 | 70 / 70 | 84 / 84 | 179 / 179 | All cases pass |
| PHP | dev-master@28079c5 | 68 / 68 | 4 / 82 | 153 / 179 | All cases pass78 failing 2.5 cases
26 failing 2.5 schema error cases
2 cases not counted
|
| Java | 2.0.2 | 70 / 70 | 2 / 84 | 147 / 179 | Errors are returned as {"code": …, "fieldValue": …} objects instead of plain error codes (the library adds the invalid value to every error), so only the codes are compared. All cases pass82 failing 2.5 cases
32 failing 2.5 schema error cases
|
| Raku | 2.3.1 | 70 / 70 | 84 / 84 | 179 / 179 | Run on Rakudo Star 2024.02: LIVR 2.1.0 no longer compiles on current Rakudo (a rx:P5 regex in LIVR::Rules::Special). All cases pass |
| Dart | 0.2.2 | 70 / 70 | 84 / 84 | 179 / 179 | All cases pass |
| Rust | 0.2.2 | 70 / 70 | 84 / 84 | 179 / 179 | All cases pass |
| Ruby | 2.1.1 | 68 / 70 | 3 / 84 | 153 / 179 | 2 failing cases
81 failing 2.5 cases
26 failing 2.5 schema error cases
|
| Go | v2.0.0+incompatible | 66 / 70 | 3 / 84 | 153 / 179 | 4 failing cases
81 failing 2.5 cases
26 failing 2.5 schema error cases
|
| Swift | 1.0.5@a362353 | 63 / 70 | 4 / 84 | 0 / 179 | Apple platforms only: it relies on NSPredicate format strings, which Foundation on Linux doesn't provide. Built from source in Swift 4.2 language mode on macOS. 7 failing cases
80 failing 2.5 cases
179 failing 2.5 schema error cases
|
| Lua | 0.5.1 | 61 / 68 | 3 / 80 | 149 / 175 | Installed with the optional lrexlib-pcre2 and luautf8 rocks, which the `like` rule and Unicode-aware to_lc/to_uc need. 7 failing cases
77 failing 2.5 cases
26 failing 2.5 schema error cases
2 cases not counted
|
| Erlang · Olifer | 2.0.2@dafdf9c | 61 / 70 | 2 / 84 | 5 / 179 | Not published on hex; built from the repository. 9 failing cases
82 failing 2.5 cases
174 failing 2.5 schema error cases
|
| Erlang · Liver | 1.1.0 | 55 / 70 | 1 / 84 | 0 / 179 | Validated with liver's `rule_set => livr_spec` mode. liver has no API for registering data-defined rule aliases, so the alias cases fail. 15 failing cases
83 failing 2.5 cases
179 failing 2.5 schema error cases
|
| Python | 2.0.1 | 53 / 70 | 4 / 84 | 153 / 179 | 17 failing cases
80 failing 2.5 cases
26 failing 2.5 schema error cases
|
Results of running the LIVR 2.0 test suite (70 cases) against the latest version of each implementation: the published package, or the default branch when it is not published. Checked on November 9, 2026. The runners live in the conformance/ directory. Some failures come from newer test cases that were added after an implementation's last release. Cases that an implementation can't pass because of its language (for example, PHP and Lua decode {} and [] to the same value) are not counted, so its score is out of the remaining cases. The "2.5" columns run the LIVR 2.5 suite with the rules added in LIVR 2.5. They are shown separately and are not part of the score: "2.5" has the validation cases (84), "2.5 schema errors" the schema cases (179), invalid rule arguments that must fail when the validator is built. A version without the 2.5 rules passes many schema cases, because it rejects every rule it does not know.
Wrote a LIVR implementation? Great!
docs/data/implementations.json and, if you can, add a test suite runner to conformance/.npm run readme to update the list in the repository README and open a pull request.