|
1 | 1 | # aboutcode |
2 | 2 | AboutCode is an umbrella project to uncover data ... about software code: |
3 | | - |
4 | | - - where does it come from? |
5 | | - - what is its license? |
6 | | - - is it secure, maintained, well coded? |
7 | | - All these are questions that are important to find answers to when there are million of free and open source software components available on the web. |
8 | | - |
| 3 | + |
| 4 | + - Where does it come from? |
| 5 | + - What is its license? |
| 6 | + - Is it secure, maintained, well coded? |
| 7 | + |
| 8 | +All these are questions that are important to find answers to when there are million of free and open source software components available on the web. |
| 9 | + |
9 | 10 | The main homepage lives at http://aboutcode.org |
10 | 11 |
|
11 | | -Interest in the Google Summer of Code 2017: AboutCode hass been accepted as a mentoring organization in 2017: https://summerofcode.withgoogle.com/organizations/ |
12 | | -See https://github.com/nexB/aboutcode/wiki/GSOC-2017 for details |
| 12 | +Interest in the Google Summer of Code 2017: AboutCode has been accepted as a mentoring organization in 2017: https://summerofcode.withgoogle.com/organizations/ |
| 13 | +See https://github.com/nexB/aboutcode/wiki/GSOC-2017 for details. |
13 | 14 |
|
14 | 15 | Each AboutCode project has its own repository: |
15 | 16 |
|
16 | | -- ScanCode: this the scanner to detect the origin and license of code and its dependencies as a command line tool. https://github.com/nexB/scancode-toolkit . The lead maintainer is @pombredanne |
| 17 | +- ScanCode: This is the scanner to detect the origin and license of code and its dependencies as a command line tool. https://github.com/nexB/scancode-toolkit . The lead maintainer is @pombredanne |
17 | 18 |
|
18 | | -- AboutCode Manager: this is a GUI-based, desktop application (based on Electron) to review the results of scans and help document conclusions. https://github.com/nexB/aboutcode-manager . The lead maintainer is @jdaguil |
| 19 | +- AboutCode Manager: This is a GUI-based, desktop application (based on Electron) to review the results of scans and help document conclusions. https://github.com/nexB/aboutcode-manager . The lead maintainer is @jdaguil |
19 | 20 |
|
20 | | -- AtributeCode: this is a command line to document the provenance of code without changing it using a small yaml file. https://github.com/nexB/attributecode/ The lead maintainer @chinyeungli |
| 21 | +- AttributeCode: This is a command line tool to document the provenance of code without changing it using a small yaml file. https://github.com/nexB/attributecode/ The lead maintainer @chinyeungli |
21 | 22 |
|
22 | | -- License Expression: this is a library to parse, analyze, compare and normalize SPDX and SPDX-like license expressions using a boolean logic expression engine. See https://spdx.org/spdx-specification-21-web-version#h.jxpfx0ykyb60 to understand what an expression is. See https://github.com/nexB/license-expression for the code. The underlying boolea engine live at https://github.com/bastikr/boolean.py . Both are co-maintained by @pombredanne |
| 23 | +- License Expression: this is a library to parse, analyze, compare and normalize SPDX and SPDX-like license expressions using a boolean logic expression engine. See https://spdx.org/spdx-specification-21-web-version#h.jxpfx0ykyb60 to understand what an expression is. See https://github.com/nexB/license-expression for the code. The underlying boolea engine live at https://github.com/bastikr/boolean.py . Both are co-maintained by @pombredanne |
23 | 24 |
|
24 | | -- TraceCode-build: this is a tool to analyze the traced execution of a build, so you can learn which files are built into binaries and ultimately deployed in your distributed software. It uses strace https://github.com/strace/strace/ to which we contribute to trace system calls on Linux and reconstruct a build graph from syscalls to find which file is used to build a binary. Maintained by @pombredanne |
| 25 | +- TraceCode-build: this is a tool to analyze the traced execution of a build, so you can learn which files are built into binaries and ultimately deployed in your distributed software. It uses strace https://github.com/strace/strace/ to which we contribute to trace system calls on Linux and reconstruct a build graph from syscalls to find which file is used to build a binary. Maintained by @pombredanne |
25 | 26 |
|
26 | | -- Conan: stands for "CONtainer ANalysis" and is a tool to analyze the straucture and provenance of software component in Docker images using static analysis. https://github.com/pombredanne/conan Maintained by @pombredanne |
| 27 | +- Conan: stands for "CONtainer ANalysis" and is a tool to analyze the structure and provenance of software component in Docker images using static analysis. https://github.com/pombredanne/conan Maintained by @pombredanne |
27 | 28 |
|
28 | | -- ABCD: or AboutCode Data is a simple set of convention to define data structures that all the AboutCode tools can understand and use to exachnge data together. The upcoming specification will live in this repository. |
| 29 | +- ABCD: or AboutCode Data is a simple set of convention to define data structures that all the AboutCode tools can understand and use to exchange data together. The upcoming specification will live in this repository. |
0 commit comments