Michael Catanzaro created an issue #392:
We had some discussion in the libcroco repo regarding a security vulnerability that has drawn considerable attention (GNOME/libcroco#8). Discussion has died down now and consensus is that instead of fixing the issue and pretending that makes the library safe to use, we should just declare EOL for libcroco and archive the entire repo.