I saw a few posts and guides for integrating Govee lights with Hubitat. What is the integration maturity compared to Hue? From the guides there was a few hoops to jump through to get Hubitat to control Govee.
The community Govee integration is awesome and actively worked on. Unfortunately, those setup hoops are required, but if followed, is a set it once and forget it thing.
The native Hue integration (edit) has been around for quite a while. Community integration (CoCoHue) has been around for a long time, too. The author has mentioned that the recent native integration has more features than his community integration. (added) Either way, very good integration options available.
The native Hue integration has been around since early 2018 and did receive a significant update about a year and a half ago with platform 2.4.0, but I'd say the integration is fairly mature at this point. The Govee integration is fairly new, about a year old and released in platform version 2.4.1. I think there could be some confusion of history or maybe just a typo, but that's the one that maybe isn't quite mature yet. 
However, the Govee LAN API is fairly limited compared to "unofficial" methods I believe the community integration(s?) use, something the built-in integration prefers to avoid. You're likely to find a wider feature set there for that reason moreso than any other.
Yeah, mixed up things. Thanks. Fixed.
I also did not mention native Govee integration, focusing on the fact that the there is a really good community integration option for the OP. More answering the title, and less the maturity part. 
Govee has 3 ways to control their devices
- Many new devices support Matter
- Govee LAN API
- Govee Developer CLOUD API
If the device supports MATTER you can use generic Matter drivers to control them
There is a buit in Hubitat Govee Integration which is relatively new and it only enables control with the LAN API. The LAN API is limited to on/off, brightness control, setting color temp or color. This is good but rather basic.
The community integration i take care of works with both the Cloud and LAN API. It is the exact same LAN API the Hubitat native integration uses. The communty integration can actually be a hybrid approach if LAN API is enabled on devices inatalled first as cloud devices. In that setup a device will use LAN API for everything possible and fall back to the developer cloud API for functions the LAN API doesn’t support.
This allows it to enable a lot more functionality then the built in integration supports. With all of this though unfortunately does come complexity. Most of the complexity really comes into play once you start to try to do scenes locally through the LAN API.
The only unofficial part of the integration is related to How to get scenes codes and submit them to devices over the LAN API. Everything else is fully documented by Govee. I made a point to tryingto avoid undocumented processes as much as possible. The problem is one of the most commom asks was to be able to start and stop scenes of the device. Until Govee revamped their API not long ago there was no documented method to do so. At this pointit is a legacy feature many folks use. In many cases I now direct folks to the Govee supported solution with the cloud API.
The big thing with the community integration is to get your Cloud ApI Key first. Once you have that and add it to the configuration of the integration app you can setup devices as you want. If you want to switch and use the LAN API for a device it is just a matter of flipping a preference on the device. It doesn't have to be complicated if you don't want it to be, but a API Key is needed.
It should also be noted the built in integration only supports light devices while the community integration supports govee Life devices such as air purifiers, humidifiers, tower fans, smart kettles, ice makers, sensor devices, and other things as well
To address the question of maturity I would just say it is ever evolving as new devices come out with unique features. Keep in mind Govee devices are wifi and not zigbee. Because of that they can have some unique functionality. As device come out that are unique I have to create drivers for them. Seems like I am creating a new driver every few months. This isn't exactly a lack of maturity but the evolving landscape of the devices.
I use the Govee community integration for a half a dozen devices mostly RGBW strip lighting and it works great. I have one set of string lights used at Christmas and also one Govee tea kettle. Works great. It may not be “fully mature” but which of us is, really.
I use the community integration to control a couple of outdoor rgb led strips. I have made use of the undocumented features so that I can use some custom scenes that I created. Once the pain of setting it up is over, and the pain is not that bad, you don't have to do it again. At that point the lights function just like any other device. If you don't want to use any custom scenes, it's even easier to setup. It's a great integration.