Skip to content
This repository has been archived by the owner on Jan 17, 2023. It is now read-only.

Upgrade nsp #4324

Closed
chenba opened this issue Apr 10, 2018 · 7 comments
Closed

Upgrade nsp #4324

chenba opened this issue Apr 10, 2018 · 7 comments

Comments

@chenba
Copy link
Collaborator

chenba commented Apr 10, 2018

This is a follow-up to #4280. The newer version of nsp is not ignoring the advisories we ask it to in .nsprc. A configuration change is probably needed.

@ghost ghost added this to the Sprint 11 (61-3) 👗 milestone Apr 12, 2018
@chenba chenba self-assigned this Apr 26, 2018
@chenba
Copy link
Collaborator Author

chenba commented Apr 26, 2018

Actually, let's wait on https://github.com/nodesecurity/nsp/issues/207 for this.

@chenba chenba removed their assignment Apr 26, 2018
@ghost ghost modified the milestones: Sprint 11 (61-3) 👗, Sprint 15 (62-3) ⚽ Apr 30, 2018
@chenba
Copy link
Collaborator Author

chenba commented May 15, 2018

Now that npm has acquired NSP: "This service remains operational for current users in its current state. No new features or fixes will be implemented." The nsp repo has been archived and that above link to the issue returns a 404. 😞

@chenba
Copy link
Collaborator Author

chenba commented May 17, 2018

Looks like npm/npm#20565 is relevant to our interest.

@pdehaan
Copy link
Collaborator

pdehaan commented Jul 6, 2018

Actually, it looks like the Node Security Platform (nsp) service is shutting down 9/30.
They recommend switching to npm@6's $ npm audit as a replacement.

@jaredhirsch
Copy link
Member

Still no update on a replacement for .nsprc in npm 6

@pdehaan
Copy link
Collaborator

pdehaan commented Jul 11, 2018

I'm not a huge fan of npm audit yet, as it seems like a poor clone of the nsp service. Plus, forcing everybody onto npm@6 seems poor.

I know some other projects are using https://snyk.io/ to manage vuln detection.

@ghost
Copy link

ghost commented Aug 2, 2018

closing in favor of #4704

@ghost ghost closed this as completed Aug 2, 2018
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants