diff --git a/CHANGELOG.rst b/CHANGELOG.rst index d115cda4b80..9a25c81aeeb 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -127,7 +127,7 @@ from ``4.0.0`` to ``4.1.0``. The changes in Output Data Structure are: directories. This is returned optionally with the ``--info`` plugin. - A new resource level attribute ``is_community`` is added, which is - True from commonly used files used for community/project maintainence. + True from commonly used files used for community/project maintenance. This is returned optionally with the ``--classify`` plugin. These are the details for the most important changes introduced:: @@ -340,7 +340,7 @@ v32.2.1 - 2024-07-02 - Add support for poetry packages, with poetry specific pyproject.toml support, poetry.lock and package assembly support. Also add support for parsing and storing resolved packages and dependency relationships - required to statically resolve poetry dependecy graphs. + required to statically resolve poetry dependency graphs. See https://github.com/nexB/scancode-toolkit/issues/2109 - Add support for pyproject.toml files in python projects. @@ -827,7 +827,7 @@ License detection: in all levels i.e. from codebase, package and resource level license detections and resource level license clues, irrespective of this CLI option being used, i.e. default with ``--licenses``. - See `license updates documentation `_ + See `license updates documentation `_ - We replaced the ``scancode --reindex-licenses`` command line option with a new separate command named ``scancode-reindex-licenses``. @@ -1278,7 +1278,7 @@ Changes: - `has_license_text` - `declared_copyrights` - `conflicting_license_categories` - - `ambigious_compound_licensing` + - `ambiguous_compound_licensing` - The fields of the summary plugin have been replaced with the following fields. An overview of the new fields can be found in the "Summary Plugin Update" diff --git a/README.rst b/README.rst index c35b142d8a2..d21f7024a98 100644 --- a/README.rst +++ b/README.rst @@ -31,7 +31,7 @@ Build and tests status ====================== We run 30,000+ tests on each commit on multiple CIs to ensure a good platform -compabitility with multiple versions of Windows, Linux and macOS. +compatibility with multiple versions of Windows, Linux and macOS. +------------+--------------+-------------------------+----------------------------+ | **Azure** | **RTD Build**| **GitHub actions Docs** | **GitHub actions Release** | diff --git a/docs/source/explanation/scancode-license-detection-updates.rst b/docs/source/explanation/scancode-license-detection-updates.rst index 88715aec887..e1824b1aea0 100644 --- a/docs/source/explanation/scancode-license-detection-updates.rst +++ b/docs/source/explanation/scancode-license-detection-updates.rst @@ -381,7 +381,7 @@ report here). We are now just reporting a flat mapping here, and all the rule details are also not present in the license match, and only available as an optional reference. -See this before/after comparision to see how the license data in results has +See this before/after comparison to see how the license data in results has evolved. Before:: @@ -536,12 +536,12 @@ This is now default with the CLI option ``--license``, which references from the match License-level Data and LicenseDB-level Data, and removes the actual data from the matches, and adds them to two top-level lists. -Comparision: Before/After license references +Comparison: Before/After license references ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ To compare how the license output data changes between when license references are not collected vs when they are collected (which is default from version 32.x), check out the before/after -comparision below. +comparison below. Before:: diff --git a/docs/source/getting-started/contribute/contributing-code.rst b/docs/source/getting-started/contribute/contributing-code.rst index fcb6f84f4f5..dc7e7e0771c 100644 --- a/docs/source/getting-started/contribute/contributing-code.rst +++ b/docs/source/getting-started/contribute/contributing-code.rst @@ -110,7 +110,7 @@ These are enabled by adding a ``--test-suite`` option to the pytest command. detection) In some cases we need to regenerate test data when expected behavious/result data -structures change, and we have an environement variable to regenerate test data. +structures change, and we have an environment variable to regenerate test data. `SCANCODE_REGEN_TEST_FIXTURES` is present in `scancode_config` and this can be set to regenerate test data for specific tests like this: @@ -124,7 +124,7 @@ If test data is regenerated, it is important to review the diff for test files a carefully go through all of it to make sure there are no unintended changes there, and then commit all the regenerated test data. -To help debug in scancode, we use logging. There are different environement variables +To help debug in scancode, we use logging. There are different environment variables you need to set to turn on logging. In packagedcode:: ``SCANCODE_DEBUG_PACKAGE=yes pytest -vvs tests/packagedcode/ --lf`` diff --git a/docs/source/reference/scancode-supported-packages.rst b/docs/source/reference/scancode-supported-packages.rst index d2ad15803f4..8a2f082ebe7 100644 --- a/docs/source/reference/scancode-supported-packages.rst +++ b/docs/source/reference/scancode-supported-packages.rst @@ -491,7 +491,7 @@ parsers in scancode-toolkit during documentation builds. - ``go_mod`` - Go - https://go.dev/ref/mod - * - Go module cheksums file + * - Go module checksums file - ``*/go.sum`` - ``golang`` - ``linux``, ``win``, ``mac`` diff --git a/docs/source/rst-snippets/cli-post-scan-options.rst b/docs/source/rst-snippets/cli-post-scan-options.rst index a38d90366cd..37b279f378e 100644 --- a/docs/source/rst-snippets/cli-post-scan-options.rst +++ b/docs/source/rst-snippets/cli-post-scan-options.rst @@ -54,7 +54,7 @@ --todo Identify license and package detections which needs review as there are potential issues with the detections. - Lists all the unique ambigious detections with references + Lists all the unique ambiguous detections with references to the file path and line numbers, detection details and review comments to help explain the detection issue. diff --git a/docs/source/rst-snippets/note-snippets/cli-output-samples.rst b/docs/source/rst-snippets/note-snippets/cli-output-samples.rst index 62375486c7a..98b42d33137 100644 --- a/docs/source/rst-snippets/note-snippets/cli-output-samples.rst +++ b/docs/source/rst-snippets/note-snippets/cli-output-samples.rst @@ -1,6 +1,6 @@ .. note:: - You can Output Scan Results in two different file formats simultaniously in one Scan. An + You can Output Scan Results in two different file formats simultaneously in one Scan. An example - ``scancode -clpieu --json-pp output.json --html output.html samples``. .. note:: diff --git a/etc/scripts/gen_requirements.py b/etc/scripts/gen_requirements.py index 1b87944239e..626b7011493 100755 --- a/etc/scripts/gen_requirements.py +++ b/etc/scripts/gen_requirements.py @@ -15,7 +15,7 @@ """ Utilities to manage requirements files. NOTE: this should use ONLY the standard library and not import anything else -because this is used for boostrapping with no requirements installed. +because this is used for bootstrapping with no requirements installed. """ diff --git a/etc/scripts/gen_requirements_dev.py b/etc/scripts/gen_requirements_dev.py index 85482056598..c005e57416c 100755 --- a/etc/scripts/gen_requirements_dev.py +++ b/etc/scripts/gen_requirements_dev.py @@ -15,7 +15,7 @@ """ Utilities to manage requirements files. NOTE: this should use ONLY the standard library and not import anything else -because this is used for boostrapping with no requirements installed. +because this is used for bootstrapping with no requirements installed. """ diff --git a/etc/scripts/utils_requirements.py b/etc/scripts/utils_requirements.py index 4bdc96c6978..be64da9c12b 100755 --- a/etc/scripts/utils_requirements.py +++ b/etc/scripts/utils_requirements.py @@ -15,7 +15,7 @@ """ Utilities to manage requirements files and call pip. NOTE: this should use ONLY the standard library and not import anything else -because this is used for boostrapping with no requirements installed. +because this is used for bootstrapping with no requirements installed. """ diff --git a/src/cluecode/copyrights.py b/src/cluecode/copyrights.py index 6d17467acf6..a6cd2be389f 100644 --- a/src/cluecode/copyrights.py +++ b/src/cluecode/copyrights.py @@ -2047,9 +2047,9 @@ def build_detection_from_node( (r'^\(?[Rr]ecoded$', 'AUTH2'), (r'^\(?[Mm]odified$', 'AUTH2'), (r'^\(?[Cc]reated$', 'AUTH2'), - # written is often mispelled + # written is often misspelled (r'^\(?[Ww]ritt?e[dn]$', 'AUTH2'), - # rewritten is often mispelled + # rewritten is often misspelled (r'^\(?[Rr]ewritt?e[dn]$', 'AUTH2'), (r'^\(?[Mm]aintained$', 'AUTH2'), (r'^\(?[Dd]eveloped$', 'AUTH2'), diff --git a/src/licensedcode/additional_license_location_provider.py b/src/licensedcode/additional_license_location_provider.py index 778958cbdd3..b3de330ef72 100644 --- a/src/licensedcode/additional_license_location_provider.py +++ b/src/licensedcode/additional_license_location_provider.py @@ -46,7 +46,7 @@ class AdditionalLicenseLocationProviderPlugin(object): Base plugin class for plugins that provide path locations for one or more keys such as the path location to a native binary executable or related system files. - A plugin is configured as it own package with proper environemnt markers + A plugin is configured as it own package with proper environment markers """ # name string under which this plugin is registered. diff --git a/src/licensedcode/detection.py b/src/licensedcode/detection.py index 34cbe582e63..63f04553217 100644 --- a/src/licensedcode/detection.py +++ b/src/licensedcode/detection.py @@ -1696,7 +1696,7 @@ def get_license_keys_from_detections(license_detections, licensing=Licensing()): def can_ignore_ambiguous_detection(license_detection): """ - Return True if the license_detection is not an ambigious detection + Return True if the license_detection is not an ambiguous detection which needs to be reviewed. A few cases are: 1. All the locations of the license detection are community files """ diff --git a/src/packagedcode/golang.py b/src/packagedcode/golang.py index c45be7a5e3a..7381354ba18 100644 --- a/src/packagedcode/golang.py +++ b/src/packagedcode/golang.py @@ -108,7 +108,7 @@ class GoSumHandler(BaseGoModuleHandler): path_patterns = ('*/go.sum',) default_package_type = 'golang' default_primary_language = 'Go' - description = 'Go module cheksums file' + description = 'Go module checksums file' documentation_url = 'https://go.dev/ref/mod#go-sum-files' @classmethod diff --git a/src/summarycode/todo.py b/src/summarycode/todo.py index 8ed5559083a..9672fbf8269 100644 --- a/src/summarycode/todo.py +++ b/src/summarycode/todo.py @@ -362,7 +362,7 @@ def dict_fields(attr, value): class PackageDetectionCategory(Enum): """ - These are the primary types of Detections which a ambigously detected + These are the primary types of Detections which a ambiguously detected package data is classified into. These are logged in PackageDetection.detection_log for verbosity. diff --git a/tests/cluecode/data/finder/url/verify.go b/tests/cluecode/data/finder/url/verify.go index beafc3b0008..08056223044 100644 --- a/tests/cluecode/data/finder/url/verify.go +++ b/tests/cluecode/data/finder/url/verify.go @@ -197,7 +197,7 @@ type VerifyOptions struct { // irrespective of this value. This matches the Windows CryptoAPI behavior, // but not the spec. KeyUsages []ExtKeyUsage - // MaxConstraintComparisions is the maximum number of comparisons to + // MaxConstraintComparisions is the maximum number of comparisions to // perform when checking a given certificate's name constraints. If // zero, a sensible default is used. This limit prevents pathological // certificates from consuming excessive amounts of CPU time when diff --git a/tests/licensedcode/data/datadriven/external/atarashi/Info-ZIP.c b/tests/licensedcode/data/datadriven/external/atarashi/Info-ZIP.c index 993eff39fb1..bea4703ee82 100755 --- a/tests/licensedcode/data/datadriven/external/atarashi/Info-ZIP.c +++ b/tests/licensedcode/data/datadriven/external/atarashi/Info-ZIP.c @@ -295,8 +295,8 @@ local int strcmpcasenosensitive_internal (fileName1,fileName2) /* Compare two filename (fileName1,fileName2). - If iCaseSenisivity = 1, comparision is case sensitivity (like strcmp) - If iCaseSenisivity = 2, comparision is not case sensitivity (like strcmpi + If iCaseSenisivity = 1, comparision is case sensitivity (like strcmp) + If iCaseSenisivity = 2, comparision is not case sensitivity (like strcmpi or strcasecmp) If iCaseSenisivity = 0, case sensitivity is defaut of your operating system (like 1 on Unix, 2 on Windows) diff --git a/tests/licensedcode/data/datadriven/external/fossology-tests/CECILL/CImg.h b/tests/licensedcode/data/datadriven/external/fossology-tests/CECILL/CImg.h index a5bbba9e617..a7139eece7e 100644 --- a/tests/licensedcode/data/datadriven/external/fossology-tests/CECILL/CImg.h +++ b/tests/licensedcode/data/datadriven/external/fossology-tests/CECILL/CImg.h @@ -5749,7 +5749,7 @@ namespace cimg_library { return 0; } - //! Print informations about %CImg environement variables. + //! Print informations about %CImg environment variables. /** Printing is done on the standard error output. **/ diff --git a/tests/licensedcode/data/datadriven/external/fossology-tests/Freeware/if_sppp.h b/tests/licensedcode/data/datadriven/external/fossology-tests/Freeware/if_sppp.h index 9794288de19..0f41878f895 100644 --- a/tests/licensedcode/data/datadriven/external/fossology-tests/Freeware/if_sppp.h +++ b/tests/licensedcode/data/datadriven/external/fossology-tests/Freeware/if_sppp.h @@ -77,7 +77,7 @@ u_char challenge[AUTHKEYLEN]; /* random challenge */ /* * Don't change the order of this. Ordering the phases this way allows -* for a comparision of ``pp_phase >= PHASE_AUTHENTICATE'' in order to + * for a comparision of ``pp_phase >= PHASE_AUTHENTICATE'' in order to * know whether LCP is up. */ enum ppp_phase { diff --git a/tests/licensedcode/data/datadriven/external/fossology-tests/info-zip/unzip.c b/tests/licensedcode/data/datadriven/external/fossology-tests/info-zip/unzip.c index 993eff39fb1..bea4703ee82 100644 --- a/tests/licensedcode/data/datadriven/external/fossology-tests/info-zip/unzip.c +++ b/tests/licensedcode/data/datadriven/external/fossology-tests/info-zip/unzip.c @@ -295,8 +295,8 @@ local int strcmpcasenosensitive_internal (fileName1,fileName2) /* Compare two filename (fileName1,fileName2). - If iCaseSenisivity = 1, comparision is case sensitivity (like strcmp) - If iCaseSenisivity = 2, comparision is not case sensitivity (like strcmpi + If iCaseSenisivity = 1, comparision is case sensitivity (like strcmp) + If iCaseSenisivity = 2, comparision is not case sensitivity (like strcmpi or strcasecmp) If iCaseSenisivity = 0, case sensitivity is defaut of your operating system (like 1 on Unix, 2 on Windows) diff --git a/tests/licensedcode/data/datadriven/external/slic-tests/unzip.c b/tests/licensedcode/data/datadriven/external/slic-tests/unzip.c index affad4bfeb2..65f7be99028 100644 --- a/tests/licensedcode/data/datadriven/external/slic-tests/unzip.c +++ b/tests/licensedcode/data/datadriven/external/slic-tests/unzip.c @@ -380,8 +380,8 @@ local int strcmpcasenosensitive_internal (const char* fileName1, const char* fil /* Compare two filename (fileName1,fileName2). - If iCaseSenisivity = 1, comparision is case sensitivity (like strcmp) - If iCaseSenisivity = 2, comparision is not case sensitivity (like strcmpi + If iCaseSenisivity = 1, comparision is case sensitivity (like strcmp) + If iCaseSenisivity = 2, comparision is not case sensitivity (like strcmpi or strcasecmp) If iCaseSenisivity = 0, case sensitivity is defaut of your operating system (like 1 on Unix, 2 on Windows) diff --git a/tests/licensedcode/data/plugin_license/license_reference/scan/unknown-ref-to-key-file-root/README.md b/tests/licensedcode/data/plugin_license/license_reference/scan/unknown-ref-to-key-file-root/README.md index 5c93a888529..6cb28bc5fc1 100644 --- a/tests/licensedcode/data/plugin_license/license_reference/scan/unknown-ref-to-key-file-root/README.md +++ b/tests/licensedcode/data/plugin_license/license_reference/scan/unknown-ref-to-key-file-root/README.md @@ -190,7 +190,7 @@ var number = bar / 2/e The above example is also correctly identified as division, because `e` is not a valid regex flag. I initially wanted to future-proof by allowing `[a-zA-Z]*` (any letter) as flags, but it is not worth it since it increases the amount of -ambigous cases. So only the standard `g`, `m`, `i`, `y` and `u` flags are +ambiguous cases. So only the standard `g`, `m`, `i`, `y` and `u` flags are allowed. This means that the above example will be identified as division as long as you don’t rename the `e` variable to some permutation of `gmiyu` 1 to 5 characters long. diff --git a/tests/packagedcode/data/plugin/help.txt b/tests/packagedcode/data/plugin/help.txt index 7128425a969..7af4bf3de4c 100755 --- a/tests/packagedcode/data/plugin/help.txt +++ b/tests/packagedcode/data/plugin/help.txt @@ -437,7 +437,7 @@ Package type: golang datasource_id: go_sum documentation URL: https://go.dev/ref/mod#go-sum-files primary language: Go - description: Go module cheksums file + description: Go module checksums file path_patterns: '*/go.sum' -------------------------------------------- Package type: golang diff --git a/tests/packagedcode/data/plugin/plugins_list_linux.txt b/tests/packagedcode/data/plugin/plugins_list_linux.txt index eb4763d6c7e..1674c9d9f33 100755 --- a/tests/packagedcode/data/plugin/plugins_list_linux.txt +++ b/tests/packagedcode/data/plugin/plugins_list_linux.txt @@ -458,7 +458,7 @@ Package type: golang datasource_id: go_sum documentation URL: https://go.dev/ref/mod#go-sum-files primary language: Go - description: Go module cheksums file + description: Go module checksums file path_patterns: '*/go.sum' -------------------------------------------- Package type: golang diff --git a/tests/packagedcode/data/pypi/solo-metadata/PKG-INFO b/tests/packagedcode/data/pypi/solo-metadata/PKG-INFO index 1eb7dbd9966..cf7fc93c95d 100644 --- a/tests/packagedcode/data/pypi/solo-metadata/PKG-INFO +++ b/tests/packagedcode/data/pypi/solo-metadata/PKG-INFO @@ -112,7 +112,7 @@ for upcoming features. Build and tests status ====================== -We run tests on multiple CIs to ensure a good platform compabitility and on +We run tests on multiple CIs to ensure a good platform compatibility and on multiple version of Windows, Linux and macOS. +--------------+--------------+--------------+ diff --git a/tests/packagedcode/data/pypi/solo-metadata/expected.json b/tests/packagedcode/data/pypi/solo-metadata/expected.json index 2c9f0948c6f..17bdac6780c 100644 --- a/tests/packagedcode/data/pypi/solo-metadata/expected.json +++ b/tests/packagedcode/data/pypi/solo-metadata/expected.json @@ -8,7 +8,7 @@ "qualifiers": {}, "subpath": null, "primary_language": "Python", - "description": "ScanCode is a tool to scan code for license, copyright, package and their documented dependencies and other interesting facts.\n================\nScanCode toolkit\n================\n\nA typical software project often reuses hundreds of third-party packages.\nLicense and origin information is not always easy to find and not normalized:\nScanCode discovers and normalizes this data for you.\n\nRead more about ScanCode here: `scancode-toolkit.readthedocs.io \n`_.\n\nCheck out the code at https://github.com/nexB/scancode-toolkit\n\n\nWhy use ScanCode?\n=================\n\n- As a **standalone command-line tool**, ScanCode is **easy to install**, run,\n and embed in your CI/CD processing pipeline.\n It runs on **Windows, macOS, and Linux**.\n\n- ScanCode is **used by several projects and organizations** such as\n the `Eclipse Foundation `_,\n `OpenEmbedded.org `_,\n the `FSFE `_,\n the `FSF `_,\n `OSS Review Toolkit `_, \n `ClearlyDefined.io `_,\n `RedHat Fabric8 analytics `_,\n and many more.\n\n- ScanCode detects licenses, copyrights, package manifests, direct dependencies,\n and more both in **source code** and **binary** files and is considered as the\n best-in-class and reference tool in this domain, re-used as the core tools for\n software composition data collection by several open source tools.\n\n- ScanCode provides the **most accurate license detection engine** and does a\n full comparison (also known as diff or red line comparison) between a database\n of license texts and your code instead of relying only on approximate regex\n patterns or probabilistic search, edit distance or machine learning.\n\n- Written in Python, ScanCode is **easy to extend with plugins** to contribute\n new and improved scanners, data summarization, package manifest parsers, and\n new outputs.\n\n- You can save your scan results as **JSON, HTML, CSV or SPDX** or create your\n own format with Jinja templates.\n\n- You can also organize and run ScanCode server-side with the\n companion `ScanCode.io web app `_\n to organize and store multiple scan projects including scripted scanning pipelines.\n\n- ScanCode is **actively maintained**, has a **growing users and contributors\n community**.\n\n- ScanCode is heavily **tested** with an automated test suite of over **20,000 tests**.\n\n- ScanCode has an extensive and growing documentation.\n\n- ScanCode can process these packages, build manifest and lockfile formats to extract metadata:\n Alpine packages, BUCK files, ABOUT files, Android apps, Autotools, Bazel, \n JavaScript Bower, Java Axis, MS Cab, Rust Cargo, Chef Chrome apps, \n PHP Composer and composer.lock, Conda, CPAN, Debian, Apple dmg,\n Java EAR, WAR, JAR, FreeBSD packages, Rubygems gemspec, Gemfile and Gemfile.lock, \n Go modules, Haxe packages, InstallShield installers, iOS apps, ISO images, \n Apache IVY, JBoss Sar, R CRAN, Apache Maven, Meteor, Mozilla extensions, \n MSI installers, JavaScript npm packages, package-lock.json, yarn.lock, \n NSIS Installers, NugGet, OPam, Cocoapods, Python PyPI setup.py, setup.cfg, and \n several related lockfile formats, semi structured README\n files such as README.android, README.chromium, README.facebook, README.google,\n README.thirdparty, RPMs, Shell Archives, Squashfs images, Java WAR, Windows executables.\n\n\nSee our `roadmap `_\nfor upcoming features.\n\n\nBuild and tests status\n======================\n\nWe run tests on multiple CIs to ensure a good platform compabitility and on\nmultiple version of Windows, Linux and macOS.\n\n+--------------+--------------+--------------+\n| **Appveyor** | **Azure** | **RTD Build**|\n+==============+==============+==============+\n| |appveyor| | |azure| | |docs-rtd| |\n+--------------+--------------+--------------+\n\n\nDocumentation\n=============\n\nThe ScanCode documentation is hosted at `scancode-toolkit.readthedocs.io `_.\n\nIf you are new to Scancode, start `here `_.\n\nOther Important Documentation Pages:\n\n- A `synopsis `_ \n of ScanCode command line options.\n\n- Tutorials on:\n\n - `How to run a scan `_\n - `How to visualize scan results `_\n\n- An exhaustive list of `all available options `_\n\n- Documentation on `Contributing to Code Development `_\n\n- Documentation on `Plugin Architecture `_\n\n- `FAQ `_\n\nSee also https://aboutcode.org for related companion projects and tools.\n\n\nInstallation\n============\n\nBefore installing ScanCode make sure that you have installed the prerequisites\nproperly. This means installing Python (Python 3.6 or higher is required).\n\nSee `prerequisites `_\nfor detailed information on the support platforms and Python versions.\n\nThere are a few common ways to `install ScanCode `_.\n\n- `*Recommended* installation as an application: Download a release archive, extract and run.\n `_\n\n- `Development installation from source code using a git clone\n `_\n\n- `Development installation as a library with \"pip install scancode-toolkit\"\n `_\n\n- `Run in a Docker container with a git clone and \"docker run\"\n `_\n\n\nQuick Start\n===========\n\nNote the `commands variation `_\nacross installation methods and platforms.\n\nYou can run an example scan printed on screen as JSON::\n\n ./scancode -clip --json-pp - samples\n\nFollow the `How to Run a Scan `_\ntutorial to perform a basic scan on the ``samples`` directory distributed by\ndefault with Scancode.\n\nSee more command examples::\n\n ./scancode --examples\n\nSee `How to select what will be detected in a scan\n`_\nand `How to specify the output format `_\nfor more information.\n\nYou can also refer to the `command line options synopsis\n`_\nand an exhaustive list of `all available command line options\n`_.\n\n\nArchive extraction\n==================\n\nBy default ScanCode does not extract files from tarballs, zip files, and\nother archives as part of the scan. The archives that exist in a codebase\nmust be extracted before running a scan: `extractcode` is a bundled utility\nbehaving as a mostly-universal archive extractor. For example, this command will\nrecursively extract the mytar.tar.bz2 tarball in the mytar.tar.bz2-extract\ndirectory::\n\n ./extractcode mytar.tar.bz2\n\nSee `all extractcode options `_\nand `how to extract archives `_ for details.\n\n\nSupport\n=======\n\nIf you have a problem, a suggestion or found a bug, please enter a ticket at:\nhttps://github.com/nexB/scancode-toolkit/issues\n\nFor discussions and chats, we have:\n\n* an official Gitter channel for `web-based chats\n `_.\n Gitter is also accessible via an `IRC bridge `_.\n There are other AboutCode project-specific channels available there too.\n\n* an official `#aboutcode` IRC channel on liberachat (server web.libera.chat).\n This channel receives build and commit notifications and can be noisy.\n You can use your favorite IRC client or use the `web chat \n `_.\n\n\nSource code and downloads\n=========================\n\n* https://github.com/nexB/scancode-toolkit/releases\n* https://github.com/nexB/scancode-toolkit.git\n* https://pypi.org/project/scancode-toolkit/\n* https://github.com/nexB/scancode-thirdparty-src.git\n\n\nLicense\n=======\n\n* Apache-2.0 as the overall license\n* CC-BY-4.0 for reference datasets (initially was in the Public Domain).\n* Multiple other secondary permissive or copyleft licenses (LGPL, MIT,\n BSD, GPL 2/3, etc.) for third-party components.\n\n\nSee the NOTICE file and the .ABOUT files that document the origin and license of\nthe third-party code used in ScanCode for more details.\n\n\n.. |appveyor| image:: https://ci.appveyor.com/api/projects/status/4webymu0l2ip8utr?svg=true\n :target: https://travis-ci.org/nexB/scancode-toolkit\n :alt: Appveyor tests status (Windows)\n\n.. |azure| image:: https://dev.azure.com/nexB/scancode-toolkit/_apis/build/status/nexB.scancode-toolkit?branchName=develop\n :target: https://dev.azure.com/nexB/scancode-toolkit/_build/latest?definitionId=1&branchName=develop\n :alt: Azure tests status (Linux, macOS, Windows)\n\n.. |docs-rtd| image:: https://readthedocs.org/projects/scancode-toolkit/badge/?version=latest\n :target: https://scancode-toolkit.readthedocs.io/en/latest/?badge=latest\n :alt: Documentation Status", + "description": "ScanCode is a tool to scan code for license, copyright, package and their documented dependencies and other interesting facts.\n================\nScanCode toolkit\n================\n\nA typical software project often reuses hundreds of third-party packages.\nLicense and origin information is not always easy to find and not normalized:\nScanCode discovers and normalizes this data for you.\n\nRead more about ScanCode here: `scancode-toolkit.readthedocs.io \n`_.\n\nCheck out the code at https://github.com/nexB/scancode-toolkit\n\n\nWhy use ScanCode?\n=================\n\n- As a **standalone command-line tool**, ScanCode is **easy to install**, run,\n and embed in your CI/CD processing pipeline.\n It runs on **Windows, macOS, and Linux**.\n\n- ScanCode is **used by several projects and organizations** such as\n the `Eclipse Foundation `_,\n `OpenEmbedded.org `_,\n the `FSFE `_,\n the `FSF `_,\n `OSS Review Toolkit `_, \n `ClearlyDefined.io `_,\n `RedHat Fabric8 analytics `_,\n and many more.\n\n- ScanCode detects licenses, copyrights, package manifests, direct dependencies,\n and more both in **source code** and **binary** files and is considered as the\n best-in-class and reference tool in this domain, re-used as the core tools for\n software composition data collection by several open source tools.\n\n- ScanCode provides the **most accurate license detection engine** and does a\n full comparison (also known as diff or red line comparison) between a database\n of license texts and your code instead of relying only on approximate regex\n patterns or probabilistic search, edit distance or machine learning.\n\n- Written in Python, ScanCode is **easy to extend with plugins** to contribute\n new and improved scanners, data summarization, package manifest parsers, and\n new outputs.\n\n- You can save your scan results as **JSON, HTML, CSV or SPDX** or create your\n own format with Jinja templates.\n\n- You can also organize and run ScanCode server-side with the\n companion `ScanCode.io web app `_\n to organize and store multiple scan projects including scripted scanning pipelines.\n\n- ScanCode is **actively maintained**, has a **growing users and contributors\n community**.\n\n- ScanCode is heavily **tested** with an automated test suite of over **20,000 tests**.\n\n- ScanCode has an extensive and growing documentation.\n\n- ScanCode can process these packages, build manifest and lockfile formats to extract metadata:\n Alpine packages, BUCK files, ABOUT files, Android apps, Autotools, Bazel, \n JavaScript Bower, Java Axis, MS Cab, Rust Cargo, Chef Chrome apps, \n PHP Composer and composer.lock, Conda, CPAN, Debian, Apple dmg,\n Java EAR, WAR, JAR, FreeBSD packages, Rubygems gemspec, Gemfile and Gemfile.lock, \n Go modules, Haxe packages, InstallShield installers, iOS apps, ISO images, \n Apache IVY, JBoss Sar, R CRAN, Apache Maven, Meteor, Mozilla extensions, \n MSI installers, JavaScript npm packages, package-lock.json, yarn.lock, \n NSIS Installers, NugGet, OPam, Cocoapods, Python PyPI setup.py, setup.cfg, and \n several related lockfile formats, semi structured README\n files such as README.android, README.chromium, README.facebook, README.google,\n README.thirdparty, RPMs, Shell Archives, Squashfs images, Java WAR, Windows executables.\n\n\nSee our `roadmap `_\nfor upcoming features.\n\n\nBuild and tests status\n======================\n\nWe run tests on multiple CIs to ensure a good platform compatibility and on\nmultiple version of Windows, Linux and macOS.\n\n+--------------+--------------+--------------+\n| **Appveyor** | **Azure** | **RTD Build**|\n+==============+==============+==============+\n| |appveyor| | |azure| | |docs-rtd| |\n+--------------+--------------+--------------+\n\n\nDocumentation\n=============\n\nThe ScanCode documentation is hosted at `scancode-toolkit.readthedocs.io `_.\n\nIf you are new to Scancode, start `here `_.\n\nOther Important Documentation Pages:\n\n- A `synopsis `_ \n of ScanCode command line options.\n\n- Tutorials on:\n\n - `How to run a scan `_\n - `How to visualize scan results `_\n\n- An exhaustive list of `all available options `_\n\n- Documentation on `Contributing to Code Development `_\n\n- Documentation on `Plugin Architecture `_\n\n- `FAQ `_\n\nSee also https://aboutcode.org for related companion projects and tools.\n\n\nInstallation\n============\n\nBefore installing ScanCode make sure that you have installed the prerequisites\nproperly. This means installing Python (Python 3.6 or higher is required).\n\nSee `prerequisites `_\nfor detailed information on the support platforms and Python versions.\n\nThere are a few common ways to `install ScanCode `_.\n\n- `*Recommended* installation as an application: Download a release archive, extract and run.\n `_\n\n- `Development installation from source code using a git clone\n `_\n\n- `Development installation as a library with \"pip install scancode-toolkit\"\n `_\n\n- `Run in a Docker container with a git clone and \"docker run\"\n `_\n\n\nQuick Start\n===========\n\nNote the `commands variation `_\nacross installation methods and platforms.\n\nYou can run an example scan printed on screen as JSON::\n\n ./scancode -clip --json-pp - samples\n\nFollow the `How to Run a Scan `_\ntutorial to perform a basic scan on the ``samples`` directory distributed by\ndefault with Scancode.\n\nSee more command examples::\n\n ./scancode --examples\n\nSee `How to select what will be detected in a scan\n`_\nand `How to specify the output format `_\nfor more information.\n\nYou can also refer to the `command line options synopsis\n`_\nand an exhaustive list of `all available command line options\n`_.\n\n\nArchive extraction\n==================\n\nBy default ScanCode does not extract files from tarballs, zip files, and\nother archives as part of the scan. The archives that exist in a codebase\nmust be extracted before running a scan: `extractcode` is a bundled utility\nbehaving as a mostly-universal archive extractor. For example, this command will\nrecursively extract the mytar.tar.bz2 tarball in the mytar.tar.bz2-extract\ndirectory::\n\n ./extractcode mytar.tar.bz2\n\nSee `all extractcode options `_\nand `how to extract archives `_ for details.\n\n\nSupport\n=======\n\nIf you have a problem, a suggestion or found a bug, please enter a ticket at:\nhttps://github.com/nexB/scancode-toolkit/issues\n\nFor discussions and chats, we have:\n\n* an official Gitter channel for `web-based chats\n `_.\n Gitter is also accessible via an `IRC bridge `_.\n There are other AboutCode project-specific channels available there too.\n\n* an official `#aboutcode` IRC channel on liberachat (server web.libera.chat).\n This channel receives build and commit notifications and can be noisy.\n You can use your favorite IRC client or use the `web chat \n `_.\n\n\nSource code and downloads\n=========================\n\n* https://github.com/nexB/scancode-toolkit/releases\n* https://github.com/nexB/scancode-toolkit.git\n* https://pypi.org/project/scancode-toolkit/\n* https://github.com/nexB/scancode-thirdparty-src.git\n\n\nLicense\n=======\n\n* Apache-2.0 as the overall license\n* CC-BY-4.0 for reference datasets (initially was in the Public Domain).\n* Multiple other secondary permissive or copyleft licenses (LGPL, MIT,\n BSD, GPL 2/3, etc.) for third-party components.\n\n\nSee the NOTICE file and the .ABOUT files that document the origin and license of\nthe third-party code used in ScanCode for more details.\n\n\n.. |appveyor| image:: https://ci.appveyor.com/api/projects/status/4webymu0l2ip8utr?svg=true\n :target: https://travis-ci.org/nexB/scancode-toolkit\n :alt: Appveyor tests status (Windows)\n\n.. |azure| image:: https://dev.azure.com/nexB/scancode-toolkit/_apis/build/status/nexB.scancode-toolkit?branchName=develop\n :target: https://dev.azure.com/nexB/scancode-toolkit/_build/latest?definitionId=1&branchName=develop\n :alt: Azure tests status (Linux, macOS, Windows)\n\n.. |docs-rtd| image:: https://readthedocs.org/projects/scancode-toolkit/badge/?version=latest\n :target: https://scancode-toolkit.readthedocs.io/en/latest/?badge=latest\n :alt: Documentation Status", "release_date": null, "parties": [ { @@ -123,7 +123,7 @@ "qualifiers": {}, "subpath": null, "primary_language": "Python", - "description": "ScanCode is a tool to scan code for license, copyright, package and their documented dependencies and other interesting facts.\n================\nScanCode toolkit\n================\n\nA typical software project often reuses hundreds of third-party packages.\nLicense and origin information is not always easy to find and not normalized:\nScanCode discovers and normalizes this data for you.\n\nRead more about ScanCode here: `scancode-toolkit.readthedocs.io \n`_.\n\nCheck out the code at https://github.com/nexB/scancode-toolkit\n\n\nWhy use ScanCode?\n=================\n\n- As a **standalone command-line tool**, ScanCode is **easy to install**, run,\n and embed in your CI/CD processing pipeline.\n It runs on **Windows, macOS, and Linux**.\n\n- ScanCode is **used by several projects and organizations** such as\n the `Eclipse Foundation `_,\n `OpenEmbedded.org `_,\n the `FSFE `_,\n the `FSF `_,\n `OSS Review Toolkit `_, \n `ClearlyDefined.io `_,\n `RedHat Fabric8 analytics `_,\n and many more.\n\n- ScanCode detects licenses, copyrights, package manifests, direct dependencies,\n and more both in **source code** and **binary** files and is considered as the\n best-in-class and reference tool in this domain, re-used as the core tools for\n software composition data collection by several open source tools.\n\n- ScanCode provides the **most accurate license detection engine** and does a\n full comparison (also known as diff or red line comparison) between a database\n of license texts and your code instead of relying only on approximate regex\n patterns or probabilistic search, edit distance or machine learning.\n\n- Written in Python, ScanCode is **easy to extend with plugins** to contribute\n new and improved scanners, data summarization, package manifest parsers, and\n new outputs.\n\n- You can save your scan results as **JSON, HTML, CSV or SPDX** or create your\n own format with Jinja templates.\n\n- You can also organize and run ScanCode server-side with the\n companion `ScanCode.io web app `_\n to organize and store multiple scan projects including scripted scanning pipelines.\n\n- ScanCode is **actively maintained**, has a **growing users and contributors\n community**.\n\n- ScanCode is heavily **tested** with an automated test suite of over **20,000 tests**.\n\n- ScanCode has an extensive and growing documentation.\n\n- ScanCode can process these packages, build manifest and lockfile formats to extract metadata:\n Alpine packages, BUCK files, ABOUT files, Android apps, Autotools, Bazel, \n JavaScript Bower, Java Axis, MS Cab, Rust Cargo, Chef Chrome apps, \n PHP Composer and composer.lock, Conda, CPAN, Debian, Apple dmg,\n Java EAR, WAR, JAR, FreeBSD packages, Rubygems gemspec, Gemfile and Gemfile.lock, \n Go modules, Haxe packages, InstallShield installers, iOS apps, ISO images, \n Apache IVY, JBoss Sar, R CRAN, Apache Maven, Meteor, Mozilla extensions, \n MSI installers, JavaScript npm packages, package-lock.json, yarn.lock, \n NSIS Installers, NugGet, OPam, Cocoapods, Python PyPI setup.py, setup.cfg, and \n several related lockfile formats, semi structured README\n files such as README.android, README.chromium, README.facebook, README.google,\n README.thirdparty, RPMs, Shell Archives, Squashfs images, Java WAR, Windows executables.\n\n\nSee our `roadmap `_\nfor upcoming features.\n\n\nBuild and tests status\n======================\n\nWe run tests on multiple CIs to ensure a good platform compabitility and on\nmultiple version of Windows, Linux and macOS.\n\n+--------------+--------------+--------------+\n| **Appveyor** | **Azure** | **RTD Build**|\n+==============+==============+==============+\n| |appveyor| | |azure| | |docs-rtd| |\n+--------------+--------------+--------------+\n\n\nDocumentation\n=============\n\nThe ScanCode documentation is hosted at `scancode-toolkit.readthedocs.io `_.\n\nIf you are new to Scancode, start `here `_.\n\nOther Important Documentation Pages:\n\n- A `synopsis `_ \n of ScanCode command line options.\n\n- Tutorials on:\n\n - `How to run a scan `_\n - `How to visualize scan results `_\n\n- An exhaustive list of `all available options `_\n\n- Documentation on `Contributing to Code Development `_\n\n- Documentation on `Plugin Architecture `_\n\n- `FAQ `_\n\nSee also https://aboutcode.org for related companion projects and tools.\n\n\nInstallation\n============\n\nBefore installing ScanCode make sure that you have installed the prerequisites\nproperly. This means installing Python (Python 3.6 or higher is required).\n\nSee `prerequisites `_\nfor detailed information on the support platforms and Python versions.\n\nThere are a few common ways to `install ScanCode `_.\n\n- `*Recommended* installation as an application: Download a release archive, extract and run.\n `_\n\n- `Development installation from source code using a git clone\n `_\n\n- `Development installation as a library with \"pip install scancode-toolkit\"\n `_\n\n- `Run in a Docker container with a git clone and \"docker run\"\n `_\n\n\nQuick Start\n===========\n\nNote the `commands variation `_\nacross installation methods and platforms.\n\nYou can run an example scan printed on screen as JSON::\n\n ./scancode -clip --json-pp - samples\n\nFollow the `How to Run a Scan `_\ntutorial to perform a basic scan on the ``samples`` directory distributed by\ndefault with Scancode.\n\nSee more command examples::\n\n ./scancode --examples\n\nSee `How to select what will be detected in a scan\n`_\nand `How to specify the output format `_\nfor more information.\n\nYou can also refer to the `command line options synopsis\n`_\nand an exhaustive list of `all available command line options\n`_.\n\n\nArchive extraction\n==================\n\nBy default ScanCode does not extract files from tarballs, zip files, and\nother archives as part of the scan. The archives that exist in a codebase\nmust be extracted before running a scan: `extractcode` is a bundled utility\nbehaving as a mostly-universal archive extractor. For example, this command will\nrecursively extract the mytar.tar.bz2 tarball in the mytar.tar.bz2-extract\ndirectory::\n\n ./extractcode mytar.tar.bz2\n\nSee `all extractcode options `_\nand `how to extract archives `_ for details.\n\n\nSupport\n=======\n\nIf you have a problem, a suggestion or found a bug, please enter a ticket at:\nhttps://github.com/nexB/scancode-toolkit/issues\n\nFor discussions and chats, we have:\n\n* an official Gitter channel for `web-based chats\n `_.\n Gitter is also accessible via an `IRC bridge `_.\n There are other AboutCode project-specific channels available there too.\n\n* an official `#aboutcode` IRC channel on liberachat (server web.libera.chat).\n This channel receives build and commit notifications and can be noisy.\n You can use your favorite IRC client or use the `web chat \n `_.\n\n\nSource code and downloads\n=========================\n\n* https://github.com/nexB/scancode-toolkit/releases\n* https://github.com/nexB/scancode-toolkit.git\n* https://pypi.org/project/scancode-toolkit/\n* https://github.com/nexB/scancode-thirdparty-src.git\n\n\nLicense\n=======\n\n* Apache-2.0 as the overall license\n* CC-BY-4.0 for reference datasets (initially was in the Public Domain).\n* Multiple other secondary permissive or copyleft licenses (LGPL, MIT,\n BSD, GPL 2/3, etc.) for third-party components.\n\n\nSee the NOTICE file and the .ABOUT files that document the origin and license of\nthe third-party code used in ScanCode for more details.\n\n\n.. |appveyor| image:: https://ci.appveyor.com/api/projects/status/4webymu0l2ip8utr?svg=true\n :target: https://travis-ci.org/nexB/scancode-toolkit\n :alt: Appveyor tests status (Windows)\n\n.. |azure| image:: https://dev.azure.com/nexB/scancode-toolkit/_apis/build/status/nexB.scancode-toolkit?branchName=develop\n :target: https://dev.azure.com/nexB/scancode-toolkit/_build/latest?definitionId=1&branchName=develop\n :alt: Azure tests status (Linux, macOS, Windows)\n\n.. |docs-rtd| image:: https://readthedocs.org/projects/scancode-toolkit/badge/?version=latest\n :target: https://scancode-toolkit.readthedocs.io/en/latest/?badge=latest\n :alt: Documentation Status", + "description": "ScanCode is a tool to scan code for license, copyright, package and their documented dependencies and other interesting facts.\n================\nScanCode toolkit\n================\n\nA typical software project often reuses hundreds of third-party packages.\nLicense and origin information is not always easy to find and not normalized:\nScanCode discovers and normalizes this data for you.\n\nRead more about ScanCode here: `scancode-toolkit.readthedocs.io \n`_.\n\nCheck out the code at https://github.com/nexB/scancode-toolkit\n\n\nWhy use ScanCode?\n=================\n\n- As a **standalone command-line tool**, ScanCode is **easy to install**, run,\n and embed in your CI/CD processing pipeline.\n It runs on **Windows, macOS, and Linux**.\n\n- ScanCode is **used by several projects and organizations** such as\n the `Eclipse Foundation `_,\n `OpenEmbedded.org `_,\n the `FSFE `_,\n the `FSF `_,\n `OSS Review Toolkit `_, \n `ClearlyDefined.io `_,\n `RedHat Fabric8 analytics `_,\n and many more.\n\n- ScanCode detects licenses, copyrights, package manifests, direct dependencies,\n and more both in **source code** and **binary** files and is considered as the\n best-in-class and reference tool in this domain, re-used as the core tools for\n software composition data collection by several open source tools.\n\n- ScanCode provides the **most accurate license detection engine** and does a\n full comparison (also known as diff or red line comparison) between a database\n of license texts and your code instead of relying only on approximate regex\n patterns or probabilistic search, edit distance or machine learning.\n\n- Written in Python, ScanCode is **easy to extend with plugins** to contribute\n new and improved scanners, data summarization, package manifest parsers, and\n new outputs.\n\n- You can save your scan results as **JSON, HTML, CSV or SPDX** or create your\n own format with Jinja templates.\n\n- You can also organize and run ScanCode server-side with the\n companion `ScanCode.io web app `_\n to organize and store multiple scan projects including scripted scanning pipelines.\n\n- ScanCode is **actively maintained**, has a **growing users and contributors\n community**.\n\n- ScanCode is heavily **tested** with an automated test suite of over **20,000 tests**.\n\n- ScanCode has an extensive and growing documentation.\n\n- ScanCode can process these packages, build manifest and lockfile formats to extract metadata:\n Alpine packages, BUCK files, ABOUT files, Android apps, Autotools, Bazel, \n JavaScript Bower, Java Axis, MS Cab, Rust Cargo, Chef Chrome apps, \n PHP Composer and composer.lock, Conda, CPAN, Debian, Apple dmg,\n Java EAR, WAR, JAR, FreeBSD packages, Rubygems gemspec, Gemfile and Gemfile.lock, \n Go modules, Haxe packages, InstallShield installers, iOS apps, ISO images, \n Apache IVY, JBoss Sar, R CRAN, Apache Maven, Meteor, Mozilla extensions, \n MSI installers, JavaScript npm packages, package-lock.json, yarn.lock, \n NSIS Installers, NugGet, OPam, Cocoapods, Python PyPI setup.py, setup.cfg, and \n several related lockfile formats, semi structured README\n files such as README.android, README.chromium, README.facebook, README.google,\n README.thirdparty, RPMs, Shell Archives, Squashfs images, Java WAR, Windows executables.\n\n\nSee our `roadmap `_\nfor upcoming features.\n\n\nBuild and tests status\n======================\n\nWe run tests on multiple CIs to ensure a good platform compatibility and on\nmultiple version of Windows, Linux and macOS.\n\n+--------------+--------------+--------------+\n| **Appveyor** | **Azure** | **RTD Build**|\n+==============+==============+==============+\n| |appveyor| | |azure| | |docs-rtd| |\n+--------------+--------------+--------------+\n\n\nDocumentation\n=============\n\nThe ScanCode documentation is hosted at `scancode-toolkit.readthedocs.io `_.\n\nIf you are new to Scancode, start `here `_.\n\nOther Important Documentation Pages:\n\n- A `synopsis `_ \n of ScanCode command line options.\n\n- Tutorials on:\n\n - `How to run a scan `_\n - `How to visualize scan results `_\n\n- An exhaustive list of `all available options `_\n\n- Documentation on `Contributing to Code Development `_\n\n- Documentation on `Plugin Architecture `_\n\n- `FAQ `_\n\nSee also https://aboutcode.org for related companion projects and tools.\n\n\nInstallation\n============\n\nBefore installing ScanCode make sure that you have installed the prerequisites\nproperly. This means installing Python (Python 3.6 or higher is required).\n\nSee `prerequisites `_\nfor detailed information on the support platforms and Python versions.\n\nThere are a few common ways to `install ScanCode `_.\n\n- `*Recommended* installation as an application: Download a release archive, extract and run.\n `_\n\n- `Development installation from source code using a git clone\n `_\n\n- `Development installation as a library with \"pip install scancode-toolkit\"\n `_\n\n- `Run in a Docker container with a git clone and \"docker run\"\n `_\n\n\nQuick Start\n===========\n\nNote the `commands variation `_\nacross installation methods and platforms.\n\nYou can run an example scan printed on screen as JSON::\n\n ./scancode -clip --json-pp - samples\n\nFollow the `How to Run a Scan `_\ntutorial to perform a basic scan on the ``samples`` directory distributed by\ndefault with Scancode.\n\nSee more command examples::\n\n ./scancode --examples\n\nSee `How to select what will be detected in a scan\n`_\nand `How to specify the output format `_\nfor more information.\n\nYou can also refer to the `command line options synopsis\n`_\nand an exhaustive list of `all available command line options\n`_.\n\n\nArchive extraction\n==================\n\nBy default ScanCode does not extract files from tarballs, zip files, and\nother archives as part of the scan. The archives that exist in a codebase\nmust be extracted before running a scan: `extractcode` is a bundled utility\nbehaving as a mostly-universal archive extractor. For example, this command will\nrecursively extract the mytar.tar.bz2 tarball in the mytar.tar.bz2-extract\ndirectory::\n\n ./extractcode mytar.tar.bz2\n\nSee `all extractcode options `_\nand `how to extract archives `_ for details.\n\n\nSupport\n=======\n\nIf you have a problem, a suggestion or found a bug, please enter a ticket at:\nhttps://github.com/nexB/scancode-toolkit/issues\n\nFor discussions and chats, we have:\n\n* an official Gitter channel for `web-based chats\n `_.\n Gitter is also accessible via an `IRC bridge `_.\n There are other AboutCode project-specific channels available there too.\n\n* an official `#aboutcode` IRC channel on liberachat (server web.libera.chat).\n This channel receives build and commit notifications and can be noisy.\n You can use your favorite IRC client or use the `web chat \n `_.\n\n\nSource code and downloads\n=========================\n\n* https://github.com/nexB/scancode-toolkit/releases\n* https://github.com/nexB/scancode-toolkit.git\n* https://pypi.org/project/scancode-toolkit/\n* https://github.com/nexB/scancode-thirdparty-src.git\n\n\nLicense\n=======\n\n* Apache-2.0 as the overall license\n* CC-BY-4.0 for reference datasets (initially was in the Public Domain).\n* Multiple other secondary permissive or copyleft licenses (LGPL, MIT,\n BSD, GPL 2/3, etc.) for third-party components.\n\n\nSee the NOTICE file and the .ABOUT files that document the origin and license of\nthe third-party code used in ScanCode for more details.\n\n\n.. |appveyor| image:: https://ci.appveyor.com/api/projects/status/4webymu0l2ip8utr?svg=true\n :target: https://travis-ci.org/nexB/scancode-toolkit\n :alt: Appveyor tests status (Windows)\n\n.. |azure| image:: https://dev.azure.com/nexB/scancode-toolkit/_apis/build/status/nexB.scancode-toolkit?branchName=develop\n :target: https://dev.azure.com/nexB/scancode-toolkit/_build/latest?definitionId=1&branchName=develop\n :alt: Azure tests status (Linux, macOS, Windows)\n\n.. |docs-rtd| image:: https://readthedocs.org/projects/scancode-toolkit/badge/?version=latest\n :target: https://scancode-toolkit.readthedocs.io/en/latest/?badge=latest\n :alt: Documentation Status", "release_date": null, "parties": [ { diff --git a/tests/textcode/data/analysis/verify.go b/tests/textcode/data/analysis/verify.go index beafc3b0008..08056223044 100644 --- a/tests/textcode/data/analysis/verify.go +++ b/tests/textcode/data/analysis/verify.go @@ -197,7 +197,7 @@ type VerifyOptions struct { // irrespective of this value. This matches the Windows CryptoAPI behavior, // but not the spec. KeyUsages []ExtKeyUsage - // MaxConstraintComparisions is the maximum number of comparisons to + // MaxConstraintComparisions is the maximum number of comparisions to // perform when checking a given certificate's name constraints. If // zero, a sensible default is used. This limit prevents pathological // certificates from consuming excessive amounts of CPU time when