- 8 minutes to read

3rd party libraries

Nodinite uses many Open-Source repositories and other 3rd party libraries with open-source licensing. This page lists them and their licences, so you can assess the licensing impact for your organization.

We may provide templates and example code (SDKs) for the following components and applications:

Nodinite Core Services, Log Agents, and Monitoring Agents use different run-times. Run-times used only by Nodinite v6 and earlier are no longer listed.

Run-time Version Major Nodinite Version Comment
.NET 10 >=7.0.40 In active development -
Supported OS versions
.NET 9 >=7.x - < 7.0.40 No longer in active use
.NET 8 Logic Apps Agent No longer in active use
.NET Framework 4.8.1 v7 agents Recommended for the v7 agents that still run on .NET Framework: BizTalk, Windows Server, Dynamics CRM, and IBM DataPower
.NET Framework 4.8 v7 agents Minimum for the same v7 .NET Framework agents
.NET Framework 3.5.1 - Required by the Microsoft BizTalk Server run-time, not a requirement for any Nodinite binary
Java run-time 21 JMX Monitoring Agent If possible, make sure to use the OpenJDK versions, NOT the Oracle versions

Important

You MUST update .NET run-time frequently to stay in support

.NET Patching notes
As documented by Microsoft, you must update almost monthly to stay supported.

FIPS 140-2 Level 2 (Code Signing)

Nodinite signs its binaries with a FIPS 140-2 Level 2 certificate; read Code Signing and Binary Integrity for how and why, and Windows FIPS Mode Compatibility to run Nodinite on Windows with FIPS mode enabled.

Why do we prefer open-source licensing?

Open-source licensing promotes freedom and puts no licensing limitations or demands on our code or your custom code. Our ambition is to also help develop the libraries we use.

Why do we NOT use pure GPL-based software?

We care about our intellectual property; GPL is a “viral” license and must be avoided at all costs. Any derivative works (programs like Nodinite) must also be licensed under the GPL. Also, any work that you would later add like custom agents, plugins etc. would also have to be licensed under the GPL.

The Nodinite JMX Monitoring Agent is built with Java on the OpenJDK, licensed under the GPL v2 with the Classpath Exception.

You might want to read more about Oracle's Java 11 trap - Use OpenJDK instead!.

List of 3rd party open source libraries in use by Nodinite

We do not generally list license information about the following Microsoft standard .NET Assemblies as they are too many and the licensing information about these are MIT.

  • Microsoft.*
  • System.*

If you have any questions about the usage of these, please get in touch with our support.

MIT License

Apache License

Microsoft Public License

BSD-2-Clause-License

BSD-3-Clause License

  • ng-table
  • Polly – Used to add resilience and transient-fault-handling support for communications with remote APIs and is used in multiple agents
  • jsdiff – Compare two messages in a Log View

PostgreSQL License (a liberal OSI-approved open-source license)

GNU General Public License, version 2, with the Classpath Exception

Syncfusion

Nodinite 6.1.0.74 and later is using Syncfusion Essential Studio for ASP.NET MVC and we have a signed EULA which grants us the right to redistribute their software. These binaries are in use for the radial tree, and BPM feature.

Microsoft Azure Architecture Icons

Nodinite Mapify (requires a Mapify license) embeds the Microsoft Azure architecture icon set so you can visually represent Azure services directly in your integration landscape diagrams.

Icons are selected through the Component Type entity in the Repository Model — the same entity also supports Font Awesome icons for non-Azure components. See What is a Component Type? for full details on the icon picker, built-in types, and how icons render in Mermaid output.

Important

The Azure icons are bundled within Nodinite and served through the application. Do not download or redistribute the icons directly from Nodinite. If you need the icon pack outside of Nodinite, obtain it from the official Microsoft Azure architecture icons page.

Licensing Requirements

Per Microsoft's icon terms of use, the following rules apply to any use of the Azure architecture icons:

  • Required statement: "Used with permission from Microsoft." — this must accompany any publication or documentation that includes the icons.
  • ✅ Permitted use: Architectural diagrams, training materials, and documentation to illustrate the specific function or relationship involving Azure products.
  • ❌ No modifications: Do not crop, flip, rotate, or otherwise distort the icons.
  • ❌ No misrepresentation: Do not use Microsoft product icons to represent your own product or service.
  • ❌ No disparagement: Use must not be defamatory or otherwise harmful to Microsoft or its products.

Microsoft retains all rights to the Azure architecture icons.

Other

Deprecated (no longer exists in later versions)

The following libraries were used in older versions of Nodinite Core Services, Log Agents, and Monitoring Agents. Nodinite v7 runs on .NET 10 / ASP.NET Core and documents its APIs with Scalar, so the WCF and ASP.NET Web API 2 era libraries below no longer ship.

Privacy Shield / Schrems II

Nodinite is usually installed in a customer-controlled environment. Nodinite itself has no functionality to move data outside the installed instance. Hence, Privacy Shield concerns are not applicable.

Please review the Nodinite Privacy Policy for other details about what information we store about you.

Log4J

Nodinite does not embed or ship Log4J binaries. Therefore, according to the current policy, customers must use a supported version of Log4J.

Known security vulnerabilities in Log4J.

Next Steps