The online evaluator uses a javascript library that should match the behavior exactly, we wanted to keep it javascript so that speed of the evaluation response was kept. If you detail the mis-matches we can get them in our javascript library.
We do have a new cli command sail jsonpath eval -f path-to-file.json -p "$.jsonPath" that uses the exact workflow golang library, that you can try out.