|
3 | 3 | How to Visualize Scan results
|
4 | 4 | =============================
|
5 | 5 |
|
6 |
| -In this simple tutorial example, we import results from a basic scan performed on the ``samples`` |
7 |
| -directory distributed by default with Scancode, and visualize the outputs through |
8 |
| -Scancode Workbench. |
| 6 | +To help visualize the scans, we have a dedicated tool `Scancode workbench <https://github.com/nexb/scancode-workbench/>`_ which is a desktop application that allows you to visualize and explore the results of one or more scans. It is a cross-platform application that runs on Windows, Mac OS X and Linux. It is built using the Electron framework and is built using Electron, Typescript & React |
| 7 | + |
| 8 | +Detailed Installation and Usage guide can be found here - :ref:`scancode-workbench:getting-started` |
9 | 9 |
|
10 | 10 | .. WARNING::
|
11 | 11 |
|
12 |
| - This tutorial uses the 3.1.1 version of Scancode Toolkit, and Scancode Workbench 3.1.0 (This |
13 |
| - beta version of ScanCode Workbench is compatible with scans from any ScanCode Toolkit develop |
14 |
| - version/branch at or after v3.0.2). If you are using an older version of Scancode Toolkit, check |
| 12 | + This tutorial uses the 32.x version of Scancode Toolkit, and Scancode Workbench 4.0.x (This version of ScanCode Workbench is compatible with scans from any ScanCode Toolkit develop |
| 13 | + version/branch at or after v32.x). If you are using an older version of Scancode Toolkit, check |
15 | 14 | respective versions of this documentation. Also refer the Scancode Workbench
|
16 | 15 | `release highlights <https://github.com/nexB/scancode-workbench/releases/>`_.
|
17 |
| - |
18 | 16 | ..
|
19 |
| - [ToDo] |
20 |
| - Add Windows/MacOS Support and remove this WARNING. |
21 |
| -
|
22 |
| -.. WARNING:: |
23 |
| - |
24 |
| - This tutorial is for Linux based systems presently. Additional Help for Windows/MacOS will be |
25 |
| - added. |
26 |
| - |
27 |
| -Setting up Scancode Workbench |
28 |
| ------------------------------ |
29 |
| - |
30 |
| -According to the Installation instructions for the Workbench, we have to install Node.js 6.x or later. |
31 |
| -Refer to Node.js install `instructions <https://nodejs.org/en/download/package-manager/>`_ here. |
32 |
| - |
33 |
| -You can also run the following commands:: |
34 |
| - |
35 |
| - sudo apt-get install -y nodejs |
36 |
| - sudo npm install [email protected] -g |
37 |
| - |
38 |
| -After ``Node.js`` and ``npm`` is installed and get the Scancode Workbench 3.1.0 tarball from the |
39 |
| -`Workbench Release Page <https://github.com/nexB/scancode-workbench/releases/tag/v3.1.0>`_. Extract |
40 |
| -the package and then launch Scancode Workbench:: |
41 |
| - |
42 |
| - ./ScanCode-Workbench |
43 |
| - |
44 |
| -This opens the Workbench. |
45 |
| - |
46 |
| -.. note:: |
47 |
| - |
48 |
| - You can also build Scancode Toolkit and Scancode Workbench from source. Clone the repository, |
49 |
| - don't forget to checkout to the specific release using ``git checkout <release>``, and follow |
50 |
| - the build instructions. You will ll also have to create a Python virtual environment. |
51 |
| - |
52 |
| - |
53 |
| - |
54 |
| -Importing Data into Scancode Workbench |
55 |
| --------------------------------------- |
56 |
| - |
57 |
| -#. Click on the ``File -> Import JSON File`` or Press ``Ctrl + I``. |
58 |
| - |
59 |
| -#. Select the file from the pop-up window. |
60 |
| - |
61 |
| -#. Select a Name and Location (where you want it later) for the .sqlite output file. |
62 |
| - |
63 |
| -.. note:: |
64 |
| - |
65 |
| - You can also import a .sqlite file you've saved in the past to load scan results. As it is much |
66 |
| - faster, once you've imported the JSON file and a corresponding SQLite file has been created, |
67 |
| - you shouldn't repeat this. Instead, import the SQLite file next time you want to visualize the |
68 |
| - same scan result. |
69 |
| - |
70 |
| -Visualization |
71 |
| -------------- |
72 |
| - |
73 |
| -Views |
74 |
| -^^^^^ |
75 |
| - |
76 |
| -Refer to the workbench documentation for more information on Visualization. |
77 |
| - |
78 |
| -The dashboard has a general overview. |
79 |
| - |
80 |
| -.. image:: /tutorials/data/workbench_dashboard.png |
81 |
| - |
82 |
| -There are three main views (They appear in the same order in the GIFs): |
83 |
| - |
84 |
| -- Chart Summary View, |
85 |
| -- Table View, |
86 |
| -- Components Summary View. |
87 |
| - |
88 |
| -.. image:: /tutorials/data/views_sample.gif |
89 |
| - |
90 |
| -Filters |
91 |
| -^^^^^^^ |
92 |
| - |
93 |
| -You can also click any file/directory on the file list located on the right, to filter the results |
94 |
| -such that it only contains results from that File/Directory. |
95 |
| - |
96 |
| -.. image:: /tutorials/data/filter_sample.gif |
97 |
| - |
98 |
| -Components |
99 |
| -^^^^^^^^^^ |
100 |
| - |
101 |
| -Refer :ref:`workbench_components` for more information on Components. |
102 |
| - |
103 |
| -In the table view, |
104 |
| - |
105 |
| -#. Apply filters by selecting Files/Directories |
106 |
| -#. Right Click on the Left Panel |
107 |
| -#. Select ``Edit Component`` |
108 |
| -#. A pop-up opens with fields, make necessary edits and Save. |
109 |
| -#. Go to the Component Summary View to see the Component. |
110 |
| - |
111 |
| -.. image:: /tutorials/data/components_sample.gif |
0 commit comments