This repository has been archived by the owner on Apr 2, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
executable file
·81 lines (71 loc) · 4.16 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<title>The SW360 Project</title>
<link rel="stylesheet" href="stylesheets/styles.css">
<link rel="stylesheet" href="stylesheets/pygment_trac.css">
<meta name="viewport" content="width=device-width">
<!--[if lt IE 9]>
<script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
</head>
<body>
<div class="wrapper">
<header>
<h1>SW360</h1>
<p>Your Open Component Hub</p>
<p class="view"><a href="https://github.com/sw360/sw360portal">View the Project on GitHub <small>sw360/sw360portal</small></a></p>
<ul>
<li><a href="https://github.com/sw360/sw360portal/zipball/master">Download <strong>ZIP File</strong></a></li>
<li><a href="https://github.com/sw360/sw360portal/tarball/master">Download <strong>TAR Ball</strong></a></li>
<li><a href="https://github.com/sw360/sw360portal">Fork On <strong>GitHub</strong></a></li>
</ul>
</header>
<section>
<h1>What is that all about</h1>
<p>
In most cases, software today is not built from scratch, but rather assembled from various prepackaged third-party software components.
As a result, organizations face the following challenges:</p>
<ul>
<li>Verifying various aspects of compliance when using third-party software components: license compliance, ECC checks, IP assessments, etc.</li>
<li>Sharing knowledge about software components and their qualities. For example, which software components should be recommended, which should be phased out based on which criteria?</li>
<li>Providing a broad overview of the components used: An organization and its supply chain management must have information about which assets are integrated into which products or solutions.</li>
</ul>
<p>
These three main use cases target different roles in an organization:
quality managers, software developers, legal counsels, software architects, R&D managers etc.
However, all these use cases share a common need for a central hub that manages insights into software components.
</p>
<p>
SW360 is an open source software project licensed under the EPL-1.0 that provides both a web application and a repository to collect,
organize and make available information about software components. It establishes a central hub for software components in an organization. SW360 allows for
</p>
<ul>
<li>tracking components used by a project/product,</li>
<li>assessing security vulnerabilities,</li>
<li>maintaining license obligations,</li>
<li>enforcing policies, and</li>
<li>generating legal documents.</li>
</ul>
<p>
For example, SW360 can trigger a clearing process in the open source compliance tool FOSSology and import the resulting clearing reporting.
Data is either stored in SW360’s database or on the fly imported from external sources. In future we plan to have federations of
SW360 instances that share selected information. Besides its web-based UI, all functionality of SW360 is available through an API that allows an
integration into existing devops tools.
</p>
<h2>Further Information</h2>
<p>
You can find more detailed information on the <a href="https://github.com/sw360/sw360portal/wiki">project wiki</a>.
</p>
</section>
<footer>
<p>The SW360 project is licensed under <a href="https://www.eclipse.org/legal/epl-v10.html">the EPL v1.0 license</a></p>
<p><small>This page is based on the Minimal Github — Theme by <a href="https://github.com/orderedlist">orderedlist</a>
and licensed <a href="http://creativecommons.org/licenses/by-sa/3.0/">CC-BY-SA-3.0 </a></small> </p>
</footer>
</div>
<script src="javascripts/scale.fix.js"></script>
</body>
</html>