lcov-result-merger MIT 17 versions

lcov-result-merger

npm Repository Homepage

Merges multiple lcov results into one

17

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mweibelmdeanjones

Keywords

lcovmochacoverallscodecoverage

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:yargs	AI (dependencies): yargs is a widely-used, reputable CLI argument parsing library; its unvetted status is a pipeline artifact, not a real risk for this package.	ai	2026/04/21
dependencies	unvetted-dep:fast-glob	AI (dependencies): fast-glob is a widely-used, reputable file globbing library; its unvetted status is a pipeline artifact, not a real risk for this package.	ai	2026/04/21

Versions (showing 17 of 17)

Version	Deps	Published
6.0.0	2 / 16	2026-04-29
5.0.1	2 / 16	2024-05-17
5.0.0	2 / 16	2023-11-20
4.1.0	3 / 13	2023-03-02
4.0.0	3 / 15	2022-11-24
3.3.0	4 / 16	2022-06-21
3.2.0	4 / 16	2022-05-23
3.1.0	3 / 13	2018-07-11
3.0.0	3 / 13	2018-05-24
2.0.0	3 / 13	2018-01-30
1.2.0	3 / 13	2016-04-27
1.1.0	3 / 10	2016-04-13
1.0.2	3 / 7	2015-01-30
1.0.1	3 / 7	2015-01-06
1.0.0	3 / 7	2014-06-27
0.0.2	1 / 0	2013-10-11
0.0.1	1 / 0	2013-05-01

v6.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.