Skip to content

Conversation

@legobeat
Copy link

@legobeat legobeat commented May 1, 2023

This is the result of running npm audit fix on current master. It contains non-breaking bumps addressing at least the following advisories:

The changes in the following PRs are contained or made outdated by this:

Closes:

Resolves advisories:

- ajv: GHSA-v88g-cgmw-v5xw
- ansi-regex: GHSA-93q8-gq69-wqmw
- decode-uri-component: GHSA-w573-4hg7-7wgq
- glob-parent: GHSA-cj88-88mr-972w
- hosted-git-info: GHSA-43f8-2h32-f4cj
- ini: GHSA-qqgx-2p2h-9c37
- json-schema: GHSA-896r-f27r-55mw
- lodash: GHSA-29mw-wpgm-hmr9
- minimist: GHSA-xvch-5gv4-984h
- path-parse: GHSA-hj48-42vr-x3v9
- qs: GHSA-hrpp-h998-j3pp
- shelljs: GHSA-64g7-mvw6-v9qj
- shelljs: GHSA-4rq4-32rv-6wp6
- y18n: GHSA-c4w7-xm78-47vh
@legobeat legobeat marked this pull request as ready for review May 1, 2023 08:38
@legobeat legobeat changed the title npm audit fix chore: npm audit fix May 1, 2023
@legobeat
Copy link
Author

legobeat commented May 1, 2023

@nickmerwin Are you still able to merge PRs and publish releases?

@tomasmax
Copy link

Will this PR be merged? I found a security alert in our project, which is coming from the request deprecated package. If I change it for node-fetch for example will you merge it @nickmerwin?

@hlovdal
Copy link

hlovdal commented Jan 3, 2026

@nickmerwin What is preventing this PR from being merged?

@afinetooth
Copy link
Contributor

Hi @hlovdal. We no longer maintain this Coveralls Integration—we've been focused on our Official Integrations since 2023.

Apologies if that was not clear from the README. I'll update it.

In the meantime, if you're looking to stay with a JavaScript-specific Language Integration, we currently recommend coveralls-next, per the JS Language Integrations page in our docs.

To be clear though, we still recommend using one of our Official Integrations over community-maintained Language Integrations, if you can, for two reasons:

  1. We can guarantee they are up-to-date with the latest Coveralls API features; and
  2. We can support your entire tool chain.

Our Official Integrations fully support Javascript-native coverage reports, among other coverage report types.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants