Avoid using JSON internally

[mati865]

Describe the bug you encountered:

Cargo-deny reports several issues when adding this crate to the tree. One of them is related to json crate that is unmaintained and unsound.
It'd be welcome if this crate could migrate to one of alternatives listed in the advisory.

The json crate is no longer used, but the JSON format is still unnecessarily used and should be refactored away.

What did you expect to happen instead?

Clean report from cargo-deny.

How did you install pyroscope-rs?

Added it as a dependency to one of the crates in the project.

---

version: pyroscope 0.5.7
os: Ubuntu 22.04

[korniltsev]

Are there any REAL problems with the library? Are there any bugs or security issues with it?

An alternative wold be to get rid of the json library alltogether.
It is currently used to pass some data withing same process from one piece of code to another, which I am not very proud of.

[korniltsev]

Pull requests are welcome ;)

[mati865]

Are there any REAL problems with the library?

It contains undefined behaviour if as_bytes is called before attach as the report mentions: maciejhirsz/json-rust#196
Since there is no visible segfault right now I assume the struct is initialized properly but that sounds a bit fragile.
So probably the only issue right now is having to explain why it's ok to ignore this specific advisory.

https://rustsec.org/advisories/RUSTSEC-2022-0081 lists some alternatives, jzon particularly looks like drop in replacement.

An alternative wold be to get rid of the json library alltogether.
It is currently used to pass some data withing same process from one piece of code to another, which I am not very proud of.

Sounds like a viable solution as well, I'll try to look into it in the near future.

[korniltsev]

I will keep the issue open as there is really no need for any json library. We should just remove it.

[mati865]

Certainly, I don’t have enough time to spend on it to understand what’s happening there and do proper refactoring.