Smithline Training Open Source License Matrix

SMITHLINE TRAINING OPEN SOURCE LICENSE MATRIX

Important: This matrix categorizes open source by license type (Permissive, Viral Light, Highly Viral and Affero) as explained in the legend following the list of licenses. This chart does not completely summarize each license. Read each license yourself and consult with an attorney before using open source.

Name of License: License Type: Name of License: License Type:

Academic Free License v 3.0 Viral Light com.oreilly.servlet (COS) package license Permissive

ACME Labs Freeware License Permissive Common Development and Distribution License 1.0 Viral Light (CDDL) Alloy Look&Feel Permissive Common Public Attribution License Version 1.0 (CPAL) Affero/Viral Light AGPLv1 ‐ Affero General Public License Version 1 Affero/Highly Viral Common Public License Version 1.0 (CPL) Viral Light AGPLv3 – GNU Affero General Public License Version 3 Affero/Highly Viral (variation of GPLv3) cURL License Permissive

ANTLR 2 License Permissive Django (BSD style) Permissive

ANTLR 3 License (BSD style) Permissive dmalloc Permissive

Apache License Version 1.1 Permissive dom4j License (BSD style) Permissive

Apache License Version 2.0 (January 2004) Permissive Exolab License (BSD‐style) Permissive

Artistic License Version 1.0 and 2.0 Viral Light Eclipse Public License v 1.0 (EPL)(successor to Common Viral Light Public License) Australian Public Licence B Version 1‐1 Permissive FreeType Project License (27 January 2006) Permissive Boost Software License (Version 1.0) Permissive gd Permissive Bouncy Castle License Permissive GNU GPL Licenses – See AGPL, LGPL and GPL BSD (2‐Clause or 3‐Clause) License Permissive GPLv2/GNU General Public License Version 2 (June 1991) Highly Viral bzip2 (30 December 2001) Permissive GPLv3/GNU General Public License Version 3 (June 2007) Highly Viral (Note: Review license text

SMITHLINE TRAINING OPEN SOURCE LICENSE MATRIX

Name of License: License Type: Name of License: License Type:

carefully; contains multiple unique restrictions and provisions which seek to libpcap Permissive limit assertion of your patent rights) libpng Copyright Notice, Disclaimer, and License Permissive ImageMagick (Apache style) Permissive MIT License Permissive Info‐ZIP License (2007‐Mar‐4) Permissive MIT‐X Permissive Inno Setup License Permissive Mktemp License Permissive INRIA Project License (BSD style) Permissive Mozilla Public License Version 1.1 and 2.0 Viral Light (Note: v1.1 contains broad Java Service Wrapper Community License (Tanuki Highly Viral (Note: Non‐standard viral patent defensive suspension clause) Software) license) MX4J License Version 1.0 Permissive JDOM License v1.11 (2004/02/06) Permissive Netscape Public License Version 1.1 Viral Light JSch BSD‐Style License Permissive Net‐SNMP Permissive Kerberos Permissive NIST‐SIP Conditions of Use Permissive LaTeX Project Public License (LPPL) Version 1.3c (May Permissive 2006) NUnit Permissive

Less License Permissive OpenLDAP Public License Permissive (v 2.8 )(17 August 2003) LGPLv2.1 ‐ GNU Lesser General Public License Version 2.1 Viral Light provided you comply with detailed restrictions for linking to libraries OpenNTPD Permissive

LGPLv3 ‐ GNU Lesser General Public License Version 3 Viral Light provided you comply with OpenSSH (v 1.19 2004/08/30) Permissive (variation of GPLv3) detailed restrictions for linking to libraries Open Software License v 3.0 Affero/Viral Light

SMITHLINE TRAINING OPEN SOURCE LICENSE MATRIX

Name of License: License Type: Name of License: License Type:

OpenSSL Permissive TeX Permissive

The OpenSymphony Software License Version 1.1 Permissive thttpd Permissive (ACME Labs Freeware License) PCRE License Permissive ViewCVS (BSD style) Permissive The PHP License Version 3.01 Permissive Vim License Highly Viral (Note: Non‐standard license PostgreSQL BSD License Permissive with variable viral reach depending on distribution method) PostgreSQL JDBC Driver License Permissive (02/09/2006) W3C® Software Notice and License (12/31/02) Permissive

Python Software Foundation License Version 2 Permissive X11‐style Permissive

Q Public License (QPL) Version 1.0 (1999) (including Highly Viral XML Parser Permissive Objective CAML exceptions) XP (James Clark) Permissive qsort.c Permissive YUI Library Permissive The Sleepycat License Highly Viral YUI_ext Permissive snprintf Permissive ( ≠ snprintf.c, which is covered under user’s choice of zlib Permissive Artistic License or GPL) Zope Public License Version 2.0 Permissive SSLeay Permissive strace Permissive

LEGEND FOR USE OF MATRIX 1. PERMISSIVE Description: A Permissive open source license provides for broad use, modification and distribution rights, with no “viral” requirement to distribute source code to any modifications or larger works. Most Common Permissive Licenses: Apache; BSD; MIT

2. VIRAL LIGHT Description: Under a Viral Light license, if you modify the open source code and then distribute your modifications, you must make the modifications available in source code form under the same open source license. Note that the definition of “modification” can be fuzzy and varies from license to license, so if you combine proprietary code with code licensed under a Viral Light license, be careful to ensure that the larger package does not constitute a modification of the code. Most Common Viral Light Licenses: Academic Free License; Artistic License; CDDL; CPL; Eclipse Public License; Mozilla Public License

3. HIGHLY VIRAL Description: Under a Highly Viral license, in addition to the requirement to release the source code of any modifications you distribute, if you combine the open source code with your own proprietary code and then distribute the combination, you may be required to release the source code to your proprietary code under the Highly Viral license. In other words, incorporating Highly Viral code into your product may require you to release source code to your entire product (including pre‐existing portions that were previously treated as proprietary and highly confidential). Highly Viral licenses may also require you to grant broad patent licenses or otherwise seek to constrain your patent rights and may contain restrictions on use of the code in consumer devices or products which contain digital rights management. Most Common Highly Viral Licenses: GPLv2 and GPLv3 Note re LGPL: Under the GNU Lesser General Public License (LGPL), if you meet detailed compliance requirements, you may link unmodified LGPL code to your proprietary code without viral effect (such that the license operates like a Viral Light license). 4. AFFERO Description: An Affero license is a viral license that defines distribution as allowing users to interact with code remotely over a network. As such, under an Affero license, use of code internally to support websites, SaaS and other hosted services may trigger obligations for you to make your proprietary source code available. The scope of viral reach differs from license‐to‐license so all use of Affero code must be very carefully scrutinized on a case by case basis. Most Common Affero Licenses: GNU Affero Public License, CPAL, Open Software License

(CONT. ON NEXT PAGE)

IMPORTANT NOTE REGARDING DISTRIBUTION OF ANY TYPE OF OPEN SOURCE Under all open source license types, when you distribute or otherwise pass along the open source code to a third party, you must provide attribution to the author of the code. This applies to further distributing the code in its original form or when you combine it with your own products. Under an Affero type license, this also applies when you allow users to access the code over a network.

The attribution requirements of each license vary, but at a minimum you will always need to provide a copyright notice and typically also a copy of the license itself (or certain provisions as identified in the license, such as warranty disclaimers). Note that you may also have additional requirements in addition to attribution, but attribution is always a minimum requirement. When distributing open source, carefully review each individual license to ensure you are complying with attribution and any other license requirements.

Disclaimer: The information contained in this document is provided for informational purposes only. It should not be considered legal advice or a substitute for legal advice, and does not create an attorney‐client relationship between you and Smithline Training. Because this information is general, it may not apply to your individual legal or factual circumstances. You should not take (or refrain from taking) any action based on the information in this document without first obtaining legal counsel.