Channels ▼
RSS

Open Source

The Road To Open Source Code Provenance


Data digging company OpenLogic has rolled out a new version of OLEX Enterprise Edition, a code analysis and audit kit designed to "uncover the provenance" of code within open source projects. In light of comments made this week by the German IT security watchdog, open source security issues may be on more corporate radars at the moment if recent warnings by the ombudsman are to be heeded.

OpenLogic notes that organizations have become much more proactive in auditing their code at the end of the development process to ensure security and open source license compliance. Today, many leading enterprises are taking it a step further and moving to audit open source code when it first enters the development process. In addition, many enterprises are beginning to release their own code as open source projects. In both situations, enterprises need a way to quickly audit an open source project to determine the provenance of the code and all licenses involved.

OpenLogic says its latest release of OLEX may provide clearer visibility into a team's project and identify only the code or components that have originated elsewhere, thereby saving time in the scanning process. OLEX also ensures that any additional license requirements associated with code that is "foreign" to the project are uncovered and reported to the user.

"We repeatedly heard from our customers that other open source scanners do not provide the clarity required to quickly and accurately determine code provenance," said Kim Weins, senior vice president of marketing at OpenLogic. "OpenLogic scanners now provide a complete picture of open source license requirements by unraveling the provenance of complex and intertwined open source components and projects."

For developers of open source software, OLEX will ensure the identification of all of the bundled projects, licenses, and obligations. It will also identify differences in obligations for different versions of OSS projects so they can select the appropriate versions.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video