gluon-remote-node.meta

Issues/PRs archive for MTRNord/gluon_remote_node
git clone git://archive.git.mtrnord.blog/MTRNord/gluon-remote-node.meta.git
Log | Files | Refs

2.json (1686B)


      1 {
      2   "number": 2,
      3   "title": "[Snyk] Fix for 1 vulnerable dependency path",
      4   "state": "merged",
      5   "diff_file": "2.diff",
      6   "author": "snyk-bot",
      7   "created_at": "2016-09-03T17:10:12Z",
      8   "closed_at": "2016-09-03T17:10:45Z",
      9   "merged_at": "2016-09-03T17:10:45Z",
     10   "base_ref": "master",
     11   "head_ref": "snyk-fix-cd5b91a4",
     12   "labels": [],
     13   "assignees": [],
     14   "requested_reviewers": [],
     15   "body": "This pull request fixes one or more vulnerable packages in the npm dependencies of this project. See the [Snyk test report](https://snyk.io/test/github/mtrnord/gluon_remote_node) for this project for details.\n\nThe PR includes:\n- `package.json` scripts and a Snyk policy (`.snyk`) file, which patch the vulnerabilities that can't be upgraded away and ignore vulnerabilities with no fixes.\n#### Vulnerabilities that will be ignored for 30 days\n\nNo sufficient upgrades or patches are available. You\u2019ll receive an alert when more fixes are released.\n- [npm:cli:20160615](https://snyk.io/vuln/npm:cli:20160615)\n\nYou can read more about Snyk's upgrade and patch logic in [Snyk's documentation](https://snyk.io/docs/using-snyk/).\n\nCheck the changes in this PR to ensure they won't cause issues with your project.\n\nStay secure,\nThe Snyk team\n\n<!--snyk:metadata:{\"type\":\"fix\",\"vulns\":[\"npm:cli:20160615\"],\"patch\":[],\"ignore\":[\"npm:cli:20160615\"],\"upgrade\":[]}-->\n\n<!-- Reviewable:start -->\n\n---\n\nThis change is [<img src=\"https://reviewable.io/review_button.svg\" height=\"34\" align=\"absmiddle\" alt=\"Reviewable\"/>](https://reviewable.io/reviews/mtrnord/gluon_remote_node/2)\n\n<!-- Reviewable:end -->\n",
     16   "comments": [],
     17   "review_comments": []
     18 }