POST: BSI recommends using ScanCode.
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
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aboutcode-org/www.aboutcode.org
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Add hover effects to adopter logos in the Community and Adopters sectionPossibly taken @riddheshkadu3637-ui claimed this 3 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Making all post button.Possibly taken @sarthaklole claimed this 90 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aboutcode-org/www.aboutcode.org#117 · 3 comments ·
-
WWW: Reduce frequency of update-releasesMay be free again @johnmhoran claimed this 71 days ago, and no pull request is open. Openci-workflow
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
aboutcode-org/www.aboutcode.org#180 · 1 assignee ·
-
DOCS: Create new AboutCode stack diagram(s)May be free again @hixvikas claimed this 72 days ago, and no pull request is open. Opendocumentation
Difficulty 5/5 Over a week Newbie friendliness 35/100
aboutcode-org/www.aboutcode.org#166 · 1 comment ·
All issues in aboutcode-org/www.aboutcode.org
Similar issues
-
bug pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pydantic/pydantic-ai#13939 ·
Maintainers usually reply within 1 day
-
self-host
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
funmusicplace/mirlo#2625 ·
Maintainers usually reply within 1 day
-
Bug Tests
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
JSPrismarine/JSPrismarine#3271 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 85/100
sindresorhus/eslint-plugin-unicorn#4034 ·
Maintainers usually reply within 1 day
-
Content:WebExt needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day