A simplifying summarizing Open Source Use Case: Can you shorten your work?

The OSCAd is intended to be used for each single open source software program or library used by a project. But if you use your open source software only internally without distributing it the OSCAd often [but not ever] offers the same conclusion: you have to do nothing but you must respect some interdictions. Test whether this can be an advantage for you:

QueryIssueAnswer
No distribution
to 3rd parties? 		Are you sure that you do not hand over any of the open source applications or libraries your project uses to any 3rd party in any sense?
Yes
No
No AGPL
licensed software?		 Are you sure that none of the open source software your project uses is licensed under the AGPL (GNU AFFERO GENERAL PUBLIC LICENSE)?
Yes
No
No software
modifications? 		Are you sure that your project does not modify any program, application, snippet, module or library of the open source software it wants to use?
Yes
No
Only OSLiC
known licenses? 		Are you sure that your project does only use open source software which has been licensed under one of the following open source licenses the OSLiC has checked: Apache-2.0, BSD-2-Clause, BSD-2-Clause, EPL-1.0, EUPL-1.1, GPL-2.0, GPL-3.0, LGPL-2.1, LGPL-3.0, MIT, MPL-2.0, MS-PL, PGL, PHP-3.0
Yes
No
 

Information for a possibly simplifying pre-check before using the OSCAd

Challenge: Sometimes a project uses many open source libs and apps.

The OSCAd is intended to be used for each single open source software program or library used by a project. That's necessary because you have to fulfill the license conditions for each single open soucre software if you want to use it compliantly. So in general, grouping is not possible.

Solution: Simplification with respect to a specific use case

But if you use the open source software only internally without distributing it to any 3rd party the OSCAd analysis often (but not in all cases) leads to the same conclusion: you have to do nothing but to respect some interdictions. This pre check

Implementation: Determine the specific case by answering 4 questions

This pre check determines whether all software packages you use are covered by this specific use case. If you can answer all these questions with yes, you will get a global todo- and interdiction-list and you won't have to call the OSCAd  for each single open source software package your project uses. Otherwise you will be redirected to the Telekom specific instance of the OSCAd

Disclaimer of Warranty

THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION

Limitation of Liability

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.