API Use Agreement

Open Hub API Terms of Use 

About the Open Hub API

The Open Hub API is a set of programming interfaces (“API Feature”) which allows you to connect to and access the Open Hub web sites (the “Sites”), offered by Black Duck Software, Inc. (“Black Duck”). We encourage you to use the API Feature to build stand-alone, mobile, or web-based applications and information displays, plug-ins, and other software (“Applications”) that use data accessed through the API Feature to deliver interesting and innovative new capabilities to your users and customers.

Your Agreement With Us

Black Duck permits access to, and use of, the API Feature subject to this API agreement, and all of the terms and conditions in the Black Duck Terms of Use (the “Terms”), located at http://blog.openhub.net/terms/ and hereby incorporated by reference (collectively, the “API Agreement”). PLEASE READ THIS API AGREEMENT CAREFULLY. BY USING THE API FEATURE YOU AGREE TO BE BOUND BY ALL OF THE TERMS AND CONDITIONS OF THIS API AGREEMENT. If you are entering into this API Agreement on behalf of a company or other legal entity, you represent that you have the authority to bind such entity, its affiliates and all users who access our Sites using the API Feature through your account to these terms and conditions, in which case the terms “you” or “your” shall refer to such entity, its affiliates and users associated with it. If you do not have such authority, or if you do not agree with these terms and conditions, you must not accept this API Agreement and may not use the API Feature.

These terms and conditions are effective as of July 18, 2012. Black Duck reserves the right to change this API Agreement from time to time without notice.  Please check this agreement periodically to see whether it has changed. If you use the API Feature after we post changes to the API Agreement, you accept the changed terms.

License Grant

Subject to the requirements of this API Agreement, Black Duck grants you a fully paid-up, limited, non-exclusive, non-assignable, non-transferable, worldwide license to use the API Feature to develop, test, support and distribute Applications to your end-users, or allow access to the Sites to your end-users through your integration of the API Feature in your Applications, only for personal non-commercial use or for internal business use, and not for academic research. If you want to use the API Feature in support of academic research, please see the Academic Use License. If you want to distribute or allow access to Applications for commercial purposes to end-users outside of your organization or company, please contact Black Duck at http://blog.openhub.net/support-2/.

Accessing the API

API Keys

In order to access the API Feature, you must be issued an API key. You must have a registered account on Open Hub to be issued an API key. Each API key is unique, and each API key is associated with an account and an Application. An account may be granted more than one API key. Each Application must use the API key assigned to it, and only that one API key, to access the API Feature. You may apply for an API key by completing the form at https://www.ohloh.net/accounts/me/api_keys/new, including a description of your intended use of the API Feature. We may, at our sole discretion, evaluate your intended use to determine whether it complies with this API Agreement, the Terms, and Black Duck Privacy Policy. Issuance of an API key does not constitute an endorsement by Black Duck, nor is it an affirmative statement from Black Duck stating that your intended use does not conflict with this API Agreement, the Terms, or Privacy Policy.

Each registered account is limited to 10 API keys under this API Agreement. Each API key is limited to 1000 requests per day. If you need more than 10 API keys for your account, or require more than 1000 requests per day for a particular Application, please contact Black Duck at http://blog.openhub.net/support-2/.

You agree not to:

  • Share your API keys with any third party.
  • Use any third party’s API keys.
  • Create or help anyone else create API keys.
  • Register multiple accounts for the purpose of obtaining additional API keys or increasing your aggregate API request limit.
  • Reverse-engineer the API Feature.
  • Circumvent the API Feature’s limits in any way.
  • Require your end-users to obtain an API key or use your end-users’ API keys to access the API Feature within your Applications.
  • Use the API Feature or the Content obtained through the API Feature in any way or for any purpose not allowed by the Terms.
  • Request or collect user names, passwords, or registered account information for the Sites from your users.
  • Obtain more Content through the API Feature than is minimally required to deliver the functionality of your Application.
  • Use or store registered account identifiers or account information for purposes other than their association with other Content obtained through the API Feature, or modify such account information without the account holder’s explicit permission.
  • Combine or aggregate analysis, ratings, rankings or synthetic metrics created and reported by the Sites with data from your Application or from other sources to create composite metrics. Synthesized or collected Content obtained through the API Feature must stand on its own.
  • Remove any copyright or other proprietary rights notices from Content obtained through the API Feature.
  • Sell, lease, sublicense or transfer Content obtained through the API Feature to any third party, directly or indirectly.
  • Charge directly or indirectly for any Content obtained through the API Feature, or for access to Content through your Application.
  • Use Content obtained through the API Feature in any advertisements or for targeting advertisements, whether the advertisements are in your Application or elsewhere.
  • Use Content obtained through the API Feature to replicate the Sites’ features or functionality or present the Content in a form substantially similar to the Sites. You agree that Black Duck has the sole right to determine whether any use of the API Feature violates this restriction.
  • Use any automated means, including without limitation such software as robots, spiders, search retrieval applications, or other mechanisms to collect or scrape the Sites in any way, except through the use of the API Feature as governed by this API Agreement, or use information obtained through the API Feature to drive or direct such automated mechanisms to collect information from other web sites, including without limitation project sites, development forges, or other hosting Sites.

We may change or suspend your access to the API Feature, or block or limit your access to all or any part of it at any time, for any reason. You agree that if, in our sole determination, you have violated this API Agreement or the Terms, we may limit, suspend, or terminate your access to the API Feature immediately, without prior notice. You understand that you are solely responsible for any and all use of the API Feature as authorized by the API keys issued to your registered account, and agree that you will indemnify us in accordance with section VIII of the Terms for your use of the API Feature.


Content obtained through the API Feature is licensed according to the Terms and the Creative Commons Attribution 3.0 Unported license (“CC-BY”). Wherever possible, you must follow all of the attribution requirements in Section V. of the Terms. Applications that may in any way be indexed by search engines must follow all of these requirements.

We offer you a worldwide, paid-up, limited use license to use the names “Open Hub” and “Open Hub Code”, the Open Hub logo including the Swirly-O, the Swirly-O logo by itself, and other designated logos and trademarks of Black Duck solely for the purpose of attribution within your Application. You must follow our guidelines, found below, when you use any of these logos or trademarks in your Application.  Black Duck reserves the right to determine, in its sole discretion, whether you have complied with the attribution requirements, have used the logos and trademarks in accordance with applicable guidelines, and have used the trademarks in ways which clearly do not indicate an endorsement of your usage by Black Duck.

General Attribution

All Applications must display a visual indication that the source of some content or data is the Site providing the API Feature. For example, Applications that call the Open Hub API must display text or graphics indicating that some content is from Open Hub. Your Application may display this indication on a splash screen when a user opens your Application, or alternatively on an “About” or “Credits” page within your Application. For example, you could display the words “Powered by” and the Open Hub logo on the Application splash screen or “About” page. If an Application can display and activate a hyperlink, then this visual display must link to the corresponding Site, for example http://www.ohloh.net. If an Application cannot link to another web location, then it must also display a text representation of the Site’s URL.

Content-Specific Attribution

All Applications must display a visual indication of the source of information obtained through the API Feature as soon as this information becomes visible in the Application. For example, an Application could display the Open Hub logo or the Swirly-O logo near such information, or the text “Content by Open Hub” or equivalent.

If an Application can trigger opening a web browser to a specific URL from within the Application, then clicking on this visual indication must open the URL on the Site corresponding to the information obtained through the API Feature. For example, a Swirly-O logo next to committer data on a particular project obtained through the Open Hub API must open that project’s summary or committer page in a browser, when clicked.

For Applications that display information from multiple sources such that attribution indicators as described above would be visually distracting, then the Application can provide a single “information”, “sources” or “credits” icon which when clicked, displays attribution indicators with links to the Site on a separate screen or view.


There are no fees for the non-commercial license granted in this API Agreement. Black Duck reserves the right to charge for this license and capability in the future. If Black Duck changes this Agreement to require a fee for this license, then you will not be obligated to continue your use of the API Feature.

Fees for FOSS Project and Organization Access

Black Duck is committed to helping foster the progress and adoption of FOSS, and the success of FOSS communities. Accordingly, we pledge not to charge a fee for use of the API Feature by FOSS projects, contributors, and organizations sponsoring FOSS projects, when used for non-commercial purposes in direct support of the project or organization. We may choose to require additional information in order to assess eligibility for such use in the future.

General Terms

Your use of the API Feature is governed by the terms and conditions of the Terms as modified by this API Agreement. Accordingly, all terms and conditions in the Terms, including but not limited to the termination provisions, Disclaimer of Warranty,  Limitation of Liability, Indemnity, Jurisdiction and Applicable Law, Waiver and Severability, and Copyright Claims sections are in effect, and all other provisions of this API Agreement, and of the Terms which survive termination, will remain in effect. Termination of your use of the API Feature shall not relieve you of any obligations arising or accruing prior to termination, or limit any liability which you otherwise have to Black Duck, including without limitation any indemnification obligations contained in this API Agreement or the Black Duck Terms of Use.


This API Agreement is a derivative work of the Creative Commons Terms, originally at http://creativecommons.org/terms and licensed under the Creative Commons Attribution 3.0 license. This statement constitutes