Open-source Chrome extensions and Manifest V3 developer libraries from Zovo, published on GitHub under the MIT licence. Read the source before you install.
Chrome extensions ship as readable source. Unlike a compiled desktop application, anything running in your browser can be unpacked and inspected, so a claim that an extension does not phone home is checkable rather than something you take on trust.
Zovo publishes source on GitHub under github.com/theluckystrike, MIT licensed where published. Published repositories include the Tab Suspender extension and the Chrome extension guide.
The same test applies to the MCP servers Zovo publishes for AI assistants at mcp.zovo.one. Each one can be run from a downloaded bundle on your own machine or from a hosted URL, and each product page links the directory its code lives in, so the invoice server and its source can be read before you point Claude at it.
Extension permissions are coarse. An extension granted access to read and change data on all sites can, in principle, read every page you open, and the store listing cannot tell you whether it does. That gap between what a permission allows and what the code actually does is where extension risk lives.
Reading the source closes it. The same gap is why Zovo keeps permission requests minimal, and why the best-of lists record what each extension asks for rather than only what it claims to do.