Skip to content
This repository has been archived by the owner on May 30, 2024. It is now read-only.

Failing nsp check: check nsp/npm audit before publishing to npm #108

Closed
jagtesh opened this issue Aug 8, 2018 · 2 comments
Closed

Failing nsp check: check nsp/npm audit before publishing to npm #108

jagtesh opened this issue Aug 8, 2018 · 2 comments

Comments

@jagtesh
Copy link

jagtesh commented Aug 8, 2018

The current version (5.2.0) has a dependency (stringstream@0.0.5) that is currently failing an nsp check. See the below screenshot:

image

The resolution is to update it to stringstream@0.0.6. I will attach a PR for this shortly.

Thanks,
Jag
@jagtesh jagtesh mentioned this issue Aug 8, 2018
Closed
@jagtesh
Copy link
Author

jagtesh commented Aug 8, 2018

Can you add nsp/npm audit to your build pipeline to check for vulnerabilities before publishing to npm?

@jagtesh jagtesh changed the title Failing nsp check Failing nsp check: check nsp/npm audit before publishing to npm Aug 8, 2018
@eli-darkly eli-darkly mentioned this issue Aug 22, 2018
Merged
@eli-darkly
Copy link
Contributor

Fixed in the 5.2.1 release.

eli-darkly added a commit that referenced this issue Nov 14, 2018
@eli-darkly
Merge pull request #108 from launchdarkly/eb/queue-tests
a0057ac 
basic tests for UpdateQueue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jagtesh @eli-darkly