Support new npm audit JSON format

[ediblecode]

It looks like npm 7+ has changed the format of the JSON returned from npm audit --json. There's a great post here that explains a lot of the details.

So this line where we get auditResult.advisories would need to traverse over auditResult.vulnerabilities etc instead, based on the presence of the new auditReportVersion field:

npm-audit-reporter-teamcity/src/reporter.ts

Line 116 in 81cba9a

Object.keys(auditResult.advisories).forEach((advisoryId) => {

To replicated, I'm using volta locally. If I run:

volta install node@14
npm -v
npm audit --json

I see npm 6 and the old JSON format that looks like:

{
"actions": [],
"advisories": {
  "SOME ID": {
    ...
  }
}
"muted": [],
  "metadata": {
    "vulnerabilities": {
      "info": 0,
      "low": 0,
      "moderate": 6,
      "high": 7,
      "critical": 0
    },
    "dependencies": 0,
    "devDependencies": 2387,
    "optionalDependencies": 25,
    "totalDependencies": 2387
  },
  "runId": "SOME GUID"
}

Then if I run

volta install node@16
npm -v
npm audit --json

I see npm 8 and the new JSON format that looks like:

{
  "auditReportVersion": 2,
  "vulnerabilities": {
    ...
  },
  "metadata": {
    "vulnerabilities": {
      "info": 0,
      "low": 0,
      "moderate": 13,
      "high": 18,
      "critical": 0,
      "total": 31
    },
    "dependencies": {
      "prod": 1,
      "dev": 2381,
      "optional": 25,
      "peer": 0,
      "peerOptional": 0,
      "total": 2381
    }
  }
}

[cy6erskunk]

Hey @ediblecode! Thanks for the report and for the link to the article, it helps a lot. It seems the logic was changed quite a bit, but I can try to come up with something. Of course, feel free to create a PR, I'd be happy to review it.

[cy6erskunk]

Done with #584, released in 0.4.0