Potential Double Free Vulnerability

[HoshinoStranding]

I have identified a potential Double Free vulnerability in the project and would like to report it to the maintainers. This vulnerability has the potential to cause unexpected application behavior, crashes.Can you please help me check it? Thank you for your effort and patience!
Below is the execution sequence of the program that may produce Double Free vulnerability .

1. clib/src/common/clib-package.c clib_package_new_from_slug_with_package_name function: On line 726, the variable "author" (a pointer to char) is freed for the first time. However, if the program goes to the "error" section on line 733, "author" may be freed again, which can lead to a Double Free vulnerability.

[r10nw7fd3]

Hi! I'm not a maintainer, but if you need someone to take a fresh look I think I can put my five cents here.
This does, in fact, look like a double free. The chances of such double free are very low, however, because
most of the conditions to goto error are valid only if a call to malloc() in some other function is unsuccessful,
and while this can happen, it is quite rare.
But it is still a possible double free, so thank you for reporting it!