POST: BSI recommends using ScanCode.

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
documentation

Research direction

Read the linked BSI PDF first, then inspect the repository’s Docusaurus/Markdown content to find the appropriate post entry point. Confirm the intended post scope from the issue title and source; done means a post accurately explains the SPDX, ScanCode LicenseDB, and LicenseRef guidance.

Written by the indexing model from the issue text.

Description

blog

From https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03183/BSI-TR-03183-2.pdf

Principles of licence identification:

  • Licences MUST be identified with their SPDX identifier. The indication is made with the so-called identifiers for licences and expressions
  • Indication of non-standardised licence identifiers: If licence identifiers cannot be found in the list from SPDX, the licence database Scancode LicenseDB AboutCode MUST be consulted next. Identifiers from this database use the prefix LicenseRef- scancode-[...] in their SPDX identifier to map the origin of the specified identifier.
  • Completely unknown licences: If a licence discovery is not available in any of the established identifier lists, the prefix LicenseRef-<licence_inventorising_entity>-[...] MUST be used according to “Annex D: SPDX License Expressions” to assign a unique (per LicenseRef namespace) licence identifier.
Dominant language
JavaScript
Stars
9
Forks
18
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/www.aboutcode.org

All issues in aboutcode-org/www.aboutcode.org

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.