)]}'
{
  "commit": "66699b814edd3fa60d74f23a831bb833fb7a3aab",
  "tree": "0b5a945c9b83fe1e3c9efb4c0378fddda743c8c1",
  "parents": [
    "3ea4419e520ea4b470dda97689cf1f840458984d"
  ],
  "author": {
    "name": "Naveen",
    "email": "172697+naveensrinivasan@users.noreply.github.com",
    "time": "Thu Jun 09 08:19:58 2022 -0500"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu Jun 09 06:19:58 2022 -0700"
  },
  "message": "chore: renovate bot setting to pin actions to a full length commit SHA (#3474)\n\n- https://docs.renovatebot.com/modules/manager/github-actions/#additional-information\r\n\r\n- Pinned actions by SHA https://github.com/ossf/scorecard/blob/main/docs/checks.md#pinned-dependencies\r\n\r\n\u003ePin actions to a full length commit SHA\r\n\r\n\u003ePinning an action to a full length commit SHA is currently the only way to use an action as an immutable release.\r\n\u003e Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action\u0027s repository,\r\n\u003e as they would need to generate a SHA-1 collision for a valid Git object payload.\r\n\r\n- https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions\r\n- https://github.com/renovatebot/.github/blob/b0c3aa85ef2bb242580f20b02b380ca532b4ce17/default.json#L13",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "30151ae7890ff24f5405fca41a6b2fdd2d7f16bd",
      "old_mode": 33188,
      "old_path": "renovate.json",
      "new_id": "845f89eabb036e17d70e7baa816722c587372c40",
      "new_mode": 33188,
      "new_path": "renovate.json"
    }
  ]
}