[Snyk] Security upgrade hexo-renderer-ejs from 0.1.1 to 2.0.0

[ekmixon]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • site/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	798/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 8.1	Remote Code Execution (RCE) SNYK-JS-EJS-2803307	Yes	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: hexo-renderer-ejs

The new version differs by 48 commits.

• 8dd9fda V2 (Use Incremental DOM meteor/blaze#45)
• deabc8b chore(deps-dev): bump eslint from 7.32.0 to 8.1.0 (We need global template hooks meteor/blaze#49)
• 5af7160 chore(deps-dev): bump mocha from 8.4.0 to 9.1.0 (Improve speed of removing templates meteor/blaze#44)
• 6beb035 Drop node 10 (Redefine this meteor/blaze#46)
• 81c9307 Upgrade to GitHub-native Dependabot ({{elsif}} or {{elseif}} or {{#elseif}} meteor/blaze#39)
• 09cb553 chore(deps-dev): bump mocha from 7.2.0 to 8.0.1 (Support dots in names of templates. meteor/blaze#38)
• ddacbfd chore(deps-dev): bump eslint from 6.8.0 to 7.0.0 (Handle repeating class names where order matters meteor/blaze#37)
• 8c2415d chore(deps-dev): bump hexo-fs from 2.0.0 to 3.0.1 ([Snyk] Fix for 1 vulnerabilities #35)
• 0b24ab5 chore(deps-dev): bump mocha from 6.2.3 to 7.1.2 ([Snyk] Fix for 26 vulnerabilities #36)
• 5ab0f81 chore(deps-dev): bump nyc from 14.1.1 to 15.0.0 ([Snyk] Security upgrade hexo from 3.3.9 to 7.2.0 #29)
• 80c3ef3 chore(deps-dev): bump eslint-config-hexo from 3.0.0 to 4.0.0 ([Snyk] Security upgrade hexo from 3.3.9 to 4.0.0 #28)
• cc5e1b6 chore(deps): bump ejs from 2.7.4 to 3.0.1 ([Snyk] Security upgrade puppeteer from 8.0.0 to 18.2.0 #26)
• 2f17874 test: update to new include syntax ([Snyk] Fix for 25 vulnerabilities #27)
• 40dd2ce Merge pull request [Snyk] Fix for 12 vulnerabilities #24 from curbengh/1.0.0
• 993f912 Merge pull request [Snyk] Security upgrade hexo from 3.3.9 to 5.0.0 #25 from hexojs/dependabot/npm_and_yarn/hexo-fs-tw-2.0.0
• 835bf57 chore(deps-dev): update hexo-fs requirement from ^1.0.0 to ^2.0.0
• 54fb943 docs(readme): add npmjs link ([Snyk] Security upgrade hexo from 3.3.9 to 3.7.0 #23)
• 2ae8360 release: 1.0.0
• 50c43fb test: replace istanbul with nyc ([Snyk] Security upgrade hexo from 3.3.9 to 3.5.0 #21)
• 105d010 chore(deps-dev): update eslint requirement from ^5.8.0 to ^6.0.1 ([Snyk] Security upgrade hexo-renderer-less from 0.1.3 to 0.2.0 #19)
• a3a3730 chore: drop node 6 (Configure Mend Bolt for GitHub #20)
• 4b32f7c chore: specify files ([Snyk] Security upgrade hexo from 3.3.9 to 5.0.0 #22)
• 7e98c2d chore(deps-dev): update mocha requirement from ^5.2.0 to ^6.0.2 ([Snyk] Security upgrade hexo-renderer-less from 0.1.3 to 0.2.0 #17)
• ce33ee8 Merge pull request [Snyk] Security upgrade hexo-renderer-less from 0.1.3 to 0.2.0 #14 from hexojs/dependabot/npm_and_yarn/mocha-tw-5.2.0

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Remote Code Execution (RCE)

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.