Update README.md

README.md

@@ -1,6 +1,12 @@
-![hypermatch logo](./logo/logo-small.png)
-
 [![SIT](https://img.shields.io/badge/SIT-awesome-blueviolet.svg)](https://jobs.schwarz)
+[![CI](https://github.com/SchwarzIT/hypermatch/actions/workflows/go-test.yml/badge.svg)](https://github.com/SchwarzIT/hypermatch/actions/workflows/go-test.yml)
+[![Go Report Card](https://goreportcard.com/badge/github.com/SchwarzIT/hypermatch)](https://goreportcard.com/report/github.com/SchwarzIT/hypermatch)
+[![Go Reference](https://pkg.go.dev/badge/github.com/schwarzit/hypermatch.svg)](https://pkg.go.dev/github.com/schwarzit/hypermatch)
+![License](https://img.shields.io/github/license/SchwarzIT/hypermatch)
+![GitHub last commit](https://img.shields.io/github/last-commit/SchwarzIT/hypermatch)
+![GitHub go.mod Go version](https://img.shields.io/github/go-mod/go-version/SchwarzIT/hypermatch)
+
+![hypermatch logo](./logo/logo-small.png)
 
 # Introduction
 Hypermatch is a Go library that allows blazing fast matching of a large number of rules to events.
@@ -256,4 +262,4 @@ The rest of the documentation uses JSON notation for easier readability.
 Nevertheless, there are a few things to consider to get maximum performance:
 - Shorten the number of fields inside the rules, the fewer conditions, the shorter is the path to find them out.
 - Try to make the **paths** as diverse as possible in events and rules. The more heterogeneous fields, the higher the performance.
-- Reduce the number of **anyOf** conditions wherever possible
+- Reduce the number of **anyOf** conditions wherever possible