Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: npm/npm-audit-report
base: 139002428f52ca5c08cbbe71e68fd31693672907
Choose a base ref
...
head repository: npm/npm-audit-report
compare: 5ca3209f81f71db1bb1310b1aef3645086595bad
Choose a head ref
  • 6 commits
  • 59 files changed
  • 1 contributor

Commits on Apr 24, 2020

  1. feat: make this method synchronous

    BREAKING CHANGE: this removes the promise return value, replacing it
    with a regular value.
    isaacs committed Apr 24, 2020
    Configuration menu
    Copy the full SHA
    620842a View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    e179501 View commit details
    Browse the repository at this point in the history
  3. simplify test fixture handling

    isaacs committed Apr 24, 2020
    Configuration menu
    Copy the full SHA
    5102576 View commit details
    Browse the repository at this point in the history

Commits on May 1, 2020

  1. Version 2 rewrite for Arborist audit data

    This is essentially a full rewrite of this module, but maintains the
    basic shape of the API and arrangement of internal functionality.
    
    The 'install' summary report now provides clearer actionable
    information, telling the user to use `npm audit --fix` only if necessary
    (and then warning them about semver major updates vs mere dep range
    breakage).  Likewise, running `npm audit fix` is only suggested if doing
    so will fix something.  If there are issues that cannot be fixed without
    removing a dependency, then we report that as well.
    
    The detail report is significantly tightened up, partly due to the
    processing that Arborist does before handing the data over to the
    reporter, and partly by virtue of showing dependency issues nested under
    the advisory issue that causes them, and the removal of the table
    borders.
    
    The JSON report is, as can be expected, changed quite significantly.
    Anyone using that today will probably have to change their approach.  It
    MAY be worth altering what npm v7 outputs for `npm audit --json` for
    this reason, opting to just dump the `arborist.auditReport.report`
    instead of passing `arborist.auditReport` to this module.  On the other
    hand, it may not be.
    
    Chalk is now used in place of console-control-strings, as the added
    control that ccs affords is not necessary, and chalk is fine.
    isaacs committed May 1, 2020
    Configuration menu
    Copy the full SHA
    1148a75 View commit details
    Browse the repository at this point in the history
  2. force color support in CI

    isaacs committed May 1, 2020
    Configuration menu
    Copy the full SHA
    afe44c6 View commit details
    Browse the repository at this point in the history
  3. 2.0.0

    isaacs committed May 1, 2020
    Configuration menu
    Copy the full SHA
    5ca3209 View commit details
    Browse the repository at this point in the history