karma-coverage
A Karma plugin. Generate code coverage.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): karmarunnerbot is the official karma-runner org automation account with a long history (4393 days) and strong approval record; this is expected for karma-runner packages. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to karmarunnerbot, the official Karma project bot account. Legitimate org-level transition in 2019. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): v2 migrated from monolithic istanbul to modular istanbul-lib-* packages — expected and well-documented change. | ai | |
| dependencies | unvetted-dep:istanbul-lib-source-maps | AI (dependencies): istanbul-lib-source-maps is a core Istanbul ecosystem package and a legitimate, expected dependency of karma-coverage. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 2.2.1 | 6 / 31 | |
| 2.2.0 | 6 / 31 | |
| 2.1.1 | 6 / 31 | |
| 2.1.0 | 6 / 31 | |
| 2.0.3 | 6 / 35 | |
| 2.0.2 | 6 / 35 | |
| 2.0.1 | 10 / 27 | |
| 2.0.0 | 10 / 27 | |
| 1.1.2 | 5 / 27 | |
| 1.1.1 | 5 / 26 | |
| 1.1.0 | 4 / 27 | |
| 1.0.0 | 4 / 27 | |
| 0.5.5 | 4 / 27 | |
| 0.5.4 | 4 / 27 | |
| 0.5.3 | 4 / 24 | |
| 0.5.2 | 4 / 23 | |
| 0.5.1 | 4 / 23 | |
| 0.5.0 | 4 / 23 | |
| 0.4.2 | 4 / 22 | |
| 0.4.1 | 4 / 16 | |
| 0.4.0 | 3 / 16 | |
| 0.3.1 | 3 / 12 | |
| 0.3.0 | 3 / 12 | |
| 0.2.7 | 4 / 12 | |
| 0.2.6 | 4 / 12 | |
| 0.2.5 | 4 / 12 | |
| 0.2.4 | 4 / 11 | |
| 0.2.3 | 4 / 11 | |
| 0.2.2 | 3 / 11 | |
| 0.2.1 | 3 / 11 | |
| 0.2.0 | 3 / 11 | |
| 0.1.5 | 3 / 11 | |
| 0.1.4 | 3 / 11 | |
| 0.1.3 | 3 / 11 | |
| 0.1.2 | 2 / 11 | |
| 0.1.1 | 2 / 11 | |
| 0.1.0 | 2 / 11 | |
| 0.0.5 | 2 / 11 | |
| 0.0.4 | 2 / 11 | |
| 0.0.3 | 2 / 10 | |
| 0.0.2 | 2 / 0 | |
| 0.0.1 | 2 / 0 |
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2019-08-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2019-08-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-05-03. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-07-07. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-05-04. This could indicate a legitimate maintainer transition or an account compromise.