I've been using Moops for my own tools for some time now. While not necessarily suitable for libraries you are uploading to CPAN it makes application development much more pleasant.
If you find your self using things like: Moo/Moose, Moo..::Types, Method::Signatures, Try::Tiny then this will fit your workflow and save you a lot of boiler-plate.
Documentation is good. Occasionally a syntax error will result in a confusing eval-based error message but apart from that it's all good!
If you experience any problems installing, check your version of "Import::Into" - my Debian-packaged one seemed to cause problems that an update fixed. Probably a non-problem by the time you read this.
Seems to work just fine for the basic case I need. Interface is easy enough to use. Code is easy to read and has tests.
Some (very) minor quibbles/observations:
1. Type-checking on the API parameters might be improved for those of us that just skim the docs :-)
2. Option to pass in html and css separately would have been good too.
3. Has built-in URI fetching for remote css (which I don't need), so code is a bit longer than necessary. If you do need it, then thats a plus.
4. Re-parses your HTML so you can't rely on maintaining non-critical whitespace, some characters will be &xxx; encoded etc.
5. Version-number is a bit odd.
Does what it's supposed to, without any fuss. Documentation is clear as is code.
Developers responded quickly to a proposed patch improving Jenkins CI integration and since the project was on github the patching process was simple.
Good documentation, pretty flexible and with a sensible interface.
You can control styling, have multiple tbody sections and add one or more rows to the bottom of the table (e.g. for totals). Table data can be pre-processed and formatted separately and converted into links if required.
Limitations: no tfoot support, you can't add rows between tbody sections (for section totals).