Installations
npm install grunt-lcov-merge2
Developer Guide
Typescript
No
Module System
N/A
Min. Node Version
>=0.10.0
Node Version
4.3.1
NPM Version
2.14.12
Score
42.2
Supply Chain
86.3
Quality
66.9
Maintenance
25
Vulnerability
95.3
License
Releases
Unable to fetch releases
Contributors
Unable to fetch Contributors
Languages
JavaScript (100%)
Developer
jacob-meacham
Download Statistics
Total Downloads
2,427
Last Day
1
Last Week
3
Last Month
7
Last Year
54
GitHub Statistics
3 Stars
67 Commits
3 Forks
3 Watching
2 Branches
1 Contributors
Package Meta Information
Latest Version
2.0.0
Package Id
grunt-lcov-merge2@2.0.0
Size
4.34 kB
NPM Version
2.14.12
Node Version
4.3.1
Total Downloads
Cumulative downloads
Total Downloads
2,427
Last day
0%
1
Compared to previous day
Last week
200%
3
Compared to previous week
Last month
40%
7
Compared to previous month
Last year
-20.6%
54
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Peer Dependencies
1
grunt-lcov-merge
Grunt plugin to merge lcov files from multiple test runs, for use with a tool like coveralls.
This fork is intended to update grunt to 1.x since the original repo seems dead.
Getting Started
This plugin requires Grunt 0.4.0
To install, add grunt-lcov-merge to your package.json. The easiest way to do that is
1npm install grunt-lcov-merge --save-dev
Once the plugin has been installed, you'll need to enable it in your Gruntfile by adding
1grunt.loadNpmTasks('grunt-lcov-merge');
You can then run with
1grunt lcovMerge
Options
emitters
Type: Array
Default: ['file']
What emitters to send the merged data to. Supported emitters are 'file', which sends the merged data to a file, and 'event', which sends it out to the 'coverage' event and can be listened to with
1grunt.event.on('coverage', function(lcov, done) {});
outputFile
Type: String
Default coverage/lcov-merge.info
If a file emitter is specified, this is the output file to pipe data to.
Example
1 grunt.initConfig({
2 jshint: {
3 src: ['Gruntfile.js', 'tasks/**/*.js', 'test/**/*.js'],
4 options: {
5 jshintrc: true
6 }
7 },
8
9 mocha_istanbul: {
10 coverage: {
11 src: 'test/**/*.spec.js',
12 options: {
13 coverageFolder: 'build/coverage',
14 reportFormats: ['lcov'],
15 }
16 }
17 },
18
19 lcovMerge: {
20 options: {
21 emitters: ['event', 'file'],
22 outputFile: 'mergeLcov.info'
23 },
24 src: ['build/coverage/*.info', 'build/coverage/**/*.info']
25 }
26 });
27
28 grunt.event.on('coverage', function(lcov, done) {
29 // See below
30 done();
31 });
32
33 grunt.loadNpmTasks('grunt-lcov-merge');
Note that grunt-lcov-merge allows for source files to be specified via any file format.
Event emitter
One of the most useful ways to consume this plugin is to use the coverage event to send the lcov data to a service like coveralls:
1grunt.event.on('coverage', function(lcov, done) { 2 require('coveralls').handleInput(lcov, function(err) { 3 if (err) { 4 return done(err); 5 } 6 done(); 7 });
Using the coveralls module means that Travis-CI can automatically send your merged LCOV to coveralls.
Version History
- 0.1.0 - Initial version
- 0.1.1 - Trim down the number of files in the distribution
- 0.1.2. - Update dependencies, work around coveralls issue.
- 0.1.3 - Documentation updates
- 1.0.0 - Official release
![Empty State](/_next/static/media/empty.e5fae2e5.png)
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
0 existing vulnerabilities detected
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 1/28 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'develop'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 4 are checked with a SAST tool
Score
3
/10
Last Scanned on 2025-01-27
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