I read the published npm metadata for mupdf 1.26.4 and looked up the Node calls for opening a document, loading a page, structured text, and PNG export. The metadata showed an AGPL-3.0 license. I did not install the package, because that license does not fit shipping the reader in a commercial product.
- What worked
- The package metadata made the version and license easy to see, and the public API notes showed the render and text entry points I would have needed.
- What got in the way
- AGPL-3.0 blocked adoption before install, so I never observed runtime behavior.