Skip to content

[RRFC] npm audit <package> for a not yet installed package #223

Closed

Description

@Christian24

Motivation ("The Why")

In some environments (aka corporate) the NPM Registry might be behind a firewall like Nexus Firewall (which automatically blocks vulnerable packages and responds to npm with status code 403. It would be nice to have the ability to query for vulnerabilities before installing a package.

Example

npm audit <package name> --remote
This would probably not have to report back a detailed report, a summary of vulnerabilities (low, moderate or high) would probably be enough.

How

Query npm audit for a not yet installed, single package.

Current Behaviour

There is nothing I am aware of.

Desired Behaviour

Report a summary of vulnerabilities for a not yet installed package back.

foo package security summary:

0 high vulnerabilities 
0 moderate vulnerabilities 
1 low vulnerability 

References

  • n/a

Activity

  1. isaacs commented on Sep 16, 2020

    @isaacs
    Contributor
    • Should be a subcommand (ie, there may be a package named "fix")
    • Maybe attach this info to npm view?
    • Getting the full advisory set for the specified package and its deps is a little more work, but probably way more useful.
    • This is semver-minor, can come in a 7.x release.
    • much easier if we restrict it to using the new bulk advisory endpoint (since it won't require generating a complete package-lock tree shape, though we'd have to do that anyway to test deps and metavulns, so maybe not much of an issue)
  2. isaacs commented on Sep 16, 2020

    @isaacs
    Contributor

    there may be a package named "fix"

    Ah yes, there is: https://www.npmjs.com/package/fix

  3. removed
    Agendawill be discussed at the Open RFC call
    on Sep 18, 2020
  4. darcyclarke commented on Sep 18, 2020

    @darcyclarke
    Contributor

    Action items

  5. Christian24 commented on Sep 18, 2020

    @Christian24
    Author

    Thanks, for the suggestions, @isaacs. I pretty much went with all of them for the RFC, @darcyclarke I opened a RFC, I would call it a draft, so if you have any comments let me know :)

  6. ruyadorno commented on Sep 23, 2020

    @ruyadorno
    Contributor

    Let's follow up with the conversation in the PR now 😊

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions