The standard package for dealing with JSON data, encoding/json, was designed as a general purpose tool. As such, it may not be the best tool for your use case.
If you have specific requirements or a specialized used case, one of the other packages that is available may be better suited.
https://pocketgophers.com/json-packages/
This uses my new format for surveying go packages. It links to the package repository and documentation, shows the current version (or head if there are no version tags), and the license.
Is there anything else you would like to see at first glance when choosing a package?