coveralls
takes json-cov output into stdin and POSTs to coveralls.io
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): lcov-parse is a legitimate, purpose-built LCOV parsing library appropriate for a coverage reporting tool like coveralls. Addition is expected and benign. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop is explained by the addition of a 'files' whitelist in package.json restricting published content to bin/lib JS files only; not a stub replacement. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by years; no provenance is expected and stable for this package. | ai | |
| phantom-deps | phantom-dep:growl | AI (phantom-deps): growl is declared but not imported anywhere in the code; it has no runtime impact and poses no execution risk for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): coveralls must invoke git commands to collect repo metadata; child_process usage in fetchGitData.js is core, documented functionality for this package. | ai | |
| dependencies | unvetted-dep:request | AI (dependencies): The `request` library is used to POST coverage data to coveralls.io — the package's primary purpose. This dependency has been present across many versions. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 5 / 6 | |
| 3.0.13 | 5 / 6 | |
| 3.0.12 | 5 / 6 | |
| 3.0.10 | 5 / 6 | |
| 3.0.9 | 5 / 6 | |
| 3.0.6 | 6 / 7 | |
| 3.0.4 | 6 / 7 | |
| 3.0.3 | 6 / 7 | |
| 2.13.2 | 5 / 7 | |
| 2.13.1 | 5 / 7 | |
| 2.13.0 | 5 / 7 | |
| 2.11.15 | 5 / 7 | |
| 2.11.13 | 5 / 7 | |
| 2.11.12 | 5 / 6 | |
| 2.11.9 | 5 / 6 | |
| 2.11.7 | 5 / 6 | |
| 2.11.5 | 4 / 6 | |
| 2.11.2 | 4 / 6 | |
| 2.11.1 | 4 / 6 | |
| 2.11.0 | 4 / 6 | |
| 2.10.1 | 4 / 6 | |
| 2.10.0 | 4 / 6 | |
| 2.8.0 | 4 / 6 | |
| 2.7.1 | 4 / 6 | |
| 2.7.0 | 4 / 6 | |
| 2.6.1 | 4 / 6 | |
| 2.6.0 | 4 / 6 | |
| 2.5.0 | 4 / 6 | |
| 2.3.0 | 4 / 6 | |
| 2.2.0 | 4 / 6 | |
| 2.0.16 | 4 / 6 | |
| 2.0.15 | 4 / 6 | |
| 2.0.11 | 4 / 4 | |
| 2.0.10 | 4 / 4 | |
| 2.0.8 | 3 / 2 | |
| 2.0.6 | 2 / 2 | |
| 2.0.1 | 1 / 2 | |
| 1.1.3 | 3 / 2 | |
| 1.1.2 | 3 / 2 | |
| 1.1.1 | 3 / 2 | |
| 1.1.0 | 3 / 2 | |
| 1.0.0 | 3 / 2 |
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.