Gathering detailed insights and metrics for @bbc/apache2-license-checker
Gathering detailed insights and metrics for @bbc/apache2-license-checker
Gathering detailed insights and metrics for @bbc/apache2-license-checker
Gathering detailed insights and metrics for @bbc/apache2-license-checker
Automated license checker for validating project dependencies for compatible Apache2 licenses.
npm install @bbc/apache2-license-checker
Typescript
Module System
Node Version
NPM Version
64
Supply Chain
95.3
Quality
79.9
Maintenance
100
Vulnerability
97.6
License
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
Apache-2.0 License
38 Commits
1 Forks
69 Watchers
2 Branches
72 Contributors
Updated on Feb 27, 2019
Latest Version
1.1.4
Package Id
@bbc/apache2-license-checker@1.1.4
Size
7.00 kB
NPM Version
6.8.0
Node Version
10.15.0
Published on
Feb 27, 2019
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
2
Automated license checker for validating project dependencies for compatible Apache2 licenses.
npm install @bbc/apache2-license-checker --save-dev
package.json
to include apache2-license-checker
as part of your test scriptFor example:
1... 2 "scripts": { 3 "test": "mocha && npm run check-licenses", 4 "check-licenses": "apache2-license-checker" 5 }, 6...
The license checker will fail with an exit code of 1
if there are any problems with the license, and will pass with an exit code of 0
if all checks are ok.
A temporary file licenses.json
will be created containing a full license analysis based on output from the license-checker
tool. You will probably want to .gitignore
this file.
If the license checker throws errors, and you've verified the errors as acceptable risks, then you may want to create an exceptions file in your local project. For example:
license-exceptions.json
{
"exceptions": {
"cosmos-deploy@*": {
"reason": "Not required, acceptable use for BBC internal deployments"
},
"cycle@1.0.3": {
"reason": "Public Domain; see: https://github.com/dscape/cycle/"
},
"map-stream@0.1.0": {
"reason": "MIT License; see: https://github.com/dominictarr/map-stream"
},
"ua-parser-js@0.7.17": {
"reason": "Public Domain; see https://github.com/faisalman/ua-parser-js"
}
}
}
To support
npm install
npm test
Modify scripts/whitelist.js
to allow additional licenses or license combinations.
Modify scripts/exceptions.js
to allow specific modules for a given reason.
Please push to a branch and raise a pull request, or fork and do the same.
In normal usage running npm run check-licenses
produces an output similar to:
Acceptable project licenses (uses):
(MIT AND CC-BY-3.0) (1)
Apache-2.0 (3)
BSD-2-Clause (1)
BSD-3-Clause (1)
ISC (15)
MIT (23)
Unlicense (1)
WTFPL (1)
Acceptable project license exceptions:
cosmos-deploy@3.1.2
Reason: Not required, acceptable use for BBC internal deployments
cycle@1.0.3
Reason: Public Domain; see: https://github.com/dscape/cycle/
map-stream@0.1.0
Reason: MIT License; see: https://github.com/dominictarr/map-stream
All licenses ok Licensed (46) Exceptions (0) Problems (0)
If there is a problem with the licenses, then expect an output similar to:
Acceptable project licenses (uses):
Apache-2.0 (3)
BSD-2-Clause (1)
BSD-3-Clause (1)
CC-BY-3.0 (1)
CC0-1.0 (1)
ISC (16)
MIT (25)
Acceptable project license exceptions:
spdx-exceptions@2.1.0
Reason: Public Domain; see https://github.com/kemitchell/spdx-exceptions.json
Problems with the licenses for these dependencies:
spdx-license-ids@3.0.0
License: CC0-1.0
Repository: https://github.com/shinnn/spdx-license-ids
Publisher: Shinnosuke Watanabe
Url: https://github.com/shinnn
Licenses not ok Licensed (46) Exceptions (1) Problems (1)
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
4 existing vulnerabilities detected
Details
Reason
Found 1/29 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More