1. IronPDF
  2. Licensing
  3. Credits

IronPDF for Node.js Software Credits

Community Projects

Beyond our own Node.js development team, there are many to thank for the success of this Node.js package.

This software project is a cohesive solution to the functional issues users face when using PDF files in Java.

To achieve the best end result at a reasonable cost to developers, our team ethically joins and makes use of community code projects wherever they give the best and most stable results. Each library is licensed fairly, as described in the linked project hubs below. Each and every community project is consistent with commercial use.

There is no need to install any additional software; everything you need to run this library is included in our download. All code is generally compiled into our software in such a way to avoid hassle and make installation easy for our customers.

Most often, we use community software projects 'as is'. Occasionally, we might find significant improvements to any of these community projects. We are glad to share our findings, specifically when those improvements may benefit other users.

Community C++ Projects

We love C++ here at Iron Software. We are always amazed how much a bit of C++ code can add so much power to a project.

We use and contribute as best we can to the following amazing software projects in a way that is completely compatible with commercial software distributions. Parts of these codebases are compiled into IronPDF to give the best HtmlToPDF and PDF editing API we can possibly offer.

We stand on the shoulders of Giants.

In particular, we are grateful to Google / Alphabet Group for the millions of dollars and tens of thousands of Engineer hours spent standardizing HTML & CSS interpretation and PDF document object models.

Community Projects and .NET NuGet Packages

Although it may have become commonplace for software publishers to overlook the use of liberally licensed source code in commercial software, we take the stance that transparency is the best policy: We have used the following software libraries in the development of this project, either as source, binary, proof of concept, or inspiration.