Gathering detailed insights and metrics for cucumber-json-merge
Gathering detailed insights and metrics for cucumber-json-merge
Gathering detailed insights and metrics for cucumber-json-merge
Gathering detailed insights and metrics for cucumber-json-merge
npm install cucumber-json-merge
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
3 Stars
126 Commits
1 Forks
3 Watching
8 Branches
1 Contributors
Updated on 19 Apr 2022
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
-1.1%
3,145
Compared to previous day
Last week
17.7%
18,876
Compared to previous week
Last month
10.2%
72,289
Compared to previous month
Last year
47%
800,374
Compared to previous year
This work was highly based on previous work from junit-merge
npm install -g cucumber-json-merge
Or just download the repository and include it in your node_modules
directly.
Usage: cucumber-json-merge [options] <report1.json> [report2.json...]
Options:
-V, --version output the version number
-d, --dir <path> merge all results in directory
-C, --createDir create the output directory if missing
-r, --recursive pass to recursively merge all results in directory
-o, --out <mergedfile> file to output to (default: ./merged-test-results.json)
-h, --help output usage information
In case you want to run this right from within nodeJS code, you should be able to include it as a library and perform the operations you want.
1cukemerge = require('cucumber-json-merge'); 2 3files = cukemerge.listJsonFiles('.', false); 4merged = cukemerge.mergeFiles(files); 5console.log(merged);
Feel free to submit issues and/or PRs! In lieu of a formal style guide, please follow existing styles.
You can find me on Twitter.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 4
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 1/21 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
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
Reason
36 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-25
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