`@gitbook/fontawesome-pro` licensing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 29k
- Forks
- 4k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 71
Description
@gitbook/embed depends on @gitbook/icons which itself has a runtime dependency on @gitbook/fontawesome-pro.
The package.json for @gitbook/fontawesome-pro specifically has a license value of UNLICENSED.
This causes compliance scanners (e.g. Aikido) to flag it as a critical license violation.
Is this intentional? If so, is there guidance on how this package is licensed?
Contributor guide
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.
Research direction
Start by inspecting the package.json for @gitbook/fontawesome-pro and tracing its dependency path from @gitbook/embed through @gitbook/icons. Check the repository’s existing licensing guidance, then document the package’s licensing status or the guidance needed to resolve the compliance scanner warning.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100