[Snyk] Upgrade hexo-renderer-less from 0.1.3 to 2.0.2 #6

snyk-bot · 2021-07-15T20:31:41Z

Snyk has created this PR to upgrade hexo-renderer-less from 0.1.3 to 2.0.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

Warning: This is a major version upgrade, and may be a breaking change.

The recommended version is 5 versions ahead of your current version.
The recommended version was released 10 months ago, on 2020-09-05.

The recommended version fixes:

Issue	PriorityScore (*)	Exploit Maturity
Prototype Override Protection Bypass npm:qs:20170213	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Prototype Pollution npm:extend:20180424	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Prototype Pollution SNYK-JS-Y18N-1021887	589/1000 Why? Has a fix available, CVSS 7.5	Proof of Concept
Arbitrary File Overwrite SNYK-JS-TAR-174125	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Prototype Pollution SNYK-JS-NUNJUCKS-1079083	589/1000 Why? Has a fix available, CVSS 7.5	Proof of Concept
Prototype Pollution SNYK-JS-LODASH-73638	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Prototype Pollution SNYK-JS-LODASH-608086	589/1000 Why? Has a fix available, CVSS 7.5	Proof of Concept
Prototype Pollution SNYK-JS-LODASH-590103	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Prototype Pollution SNYK-JS-LODASH-450202	589/1000 Why? Has a fix available, CVSS 7.5	Proof of Concept
Command Injection SNYK-JS-LODASH-1040724	589/1000 Why? Has a fix available, CVSS 7.5	Proof of Concept
Arbitrary Code Execution SNYK-JS-JSYAML-174129	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Prototype Pollution SNYK-JS-INI-1048974	589/1000 Why? Has a fix available, CVSS 7.5	Proof of Concept
Prototype Pollution SNYK-JS-AJV-584908	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Regular Expression Denial of Service (ReDoS) npm:uglify-js:20151024	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Uninitialized Memory Exposure npm:tunnel-agent:20170305	589/1000 Why? Has a fix available, CVSS 7.5	Proof of Concept
Remote Memory Exposure npm:request:20160119	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Regular Expression Denial of Service (ReDoS) npm:moment:20161019	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Denial of Service (DoS) npm:mem:20180117	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Timing Attack npm:http-signature:20150122	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Prototype Pollution npm:hoek:20180212	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Time of Check Time of Use (TOCTOU) npm:chownr:20180731	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Prototype Pollution SNYK-JS-YARGSPARSER-560381	589/1000 Why? Has a fix available, CVSS 7.5	Proof of Concept
Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHPARSE-1077067	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Arbitrary Code Injection SNYK-JS-MORGAN-72579	589/1000 Why? Has a fix available, CVSS 7.5	Proof of Concept
Regular Expression Denial of Service (ReDoS) SNYK-JS-LODASH-73639	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Prototype Pollution SNYK-JS-LODASH-567746	589/1000 Why? Has a fix available, CVSS 7.5	Proof of Concept
Regular Expression Denial of Service (ReDoS) SNYK-JS-LODASH-1018905	589/1000 Why? Has a fix available, CVSS 7.5	Proof of Concept
Denial of Service (DoS) SNYK-JS-JSYAML-173999	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Prototype Pollution SNYK-JS-HIGHLIGHTJS-1045326	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Remote Code Execution (RCE) SNYK-JS-BUNYAN-573166	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Regular Expression Denial of Service (ReDoS) npm:moment:20170905	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Regular Expression Denial of Service (ReDoS) npm:hawk:20160119	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Regular Expression Denial of Service (ReDoS) npm:clean-css:20180306	589/1000 Why? Has a fix available, CVSS 7.5	Proof of Concept
Regular Expression Denial of Service (ReDoS) npm:braces:20180219	589/1000 Why? Has a fix available, CVSS 7.5	Proof of Concept
Reverse Tabnabbing SNYK-JS-SHOWDOWN-469487	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit
Validation Bypass SNYK-JS-KINDOF-537849	589/1000 Why? Has a fix available, CVSS 7.5	Proof of Concept

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

Release notes

Package name: hexo-renderer-less

2.0.2 - 2020-09-05
Fix
- fix: enable disableNunjucks to avoid rendering nunjucks tag [#52]
  - it's now safe to use:
```
div::before {
  content: "{{}}";
}
```
2.0.1 - 2020-08-19
FIx
- fix: set default config in renderer [#49]
2.0.0 - 2020-08-18
Breaking changes
- Drop Node 8 [#48] [#44]
- compress option has been deprecated [#30]
  - Deprecated by upstream.
Features
- feat: support Less.js options [#47]
  - Support Less.js options
  - Example:
```
less:
  options:
    globalVars:
      var1: 'some value'
```
- feat: supports globbing [#37]
  - Example:
```
less:
  paths:
    - '**/css/variables/*'
```
Dependencies
- chore(deps-dev): bump mocha from 6.8.0 to 8.0.1 [#45] [#44]
- chore(deps-dev): bump mocha from 6.2.2 to 7.1.1 [#42]
- chore(deps-dev): bump nyc from 14.1.1 to 15.0.0 [#38]
- chore(dev-deps): update eslint-config-hexo from 3.0.0 to 4.1.0 [#34]
1.0.0 - 2018-11-30
Breaking changes
- updated less to 3.9.0, see the changelog of less.
0.2.0 - 2016-06-28
No content.
0.1.3 - 2015-04-06
No content.

from hexo-renderer-less GitHub release notes

Commit messages

Package name: hexo-renderer-less

e3e9192 Merge pull request Fix slack url meteor/blaze#54 from curbengh/v2.0.2
36a5195 release: 2.0.2
faf4891 Merge pull request [Bug] Blaze: hidden html attribute does not work properly meteor/blaze#52 from curbengh/disable-nunjucks
ea17387 test: disableNunjucks
bf4f927 fix: enable disableNunjucks to avoid rendering nunjucks tag
bc68557 Merge pull request Slack join page not working meteor/blaze#51 from curbengh/globbing-docs
d906bfa docs: mention globbing
6e48871 Merge pull request Add {{elseif}} sugar syntax meteor/blaze#50 from curbengh/v2.0.1
fd28be1 release: 2.0.1
1fb3ebe Merge pull request We need global template hooks meteor/blaze#49 from curbengh/fix-config
7cec4c6 fix: set default config in renderer
2b57a2e Merge pull request Data context in a for each loop not properly set meteor/blaze#48 from curbengh/v2.0.0
30e13a5 release: 2.0.0
e097f05 chore: requires Node 10.13+
6a54343 ci(travis): specify Node 14
b46eb40 Merge pull request [Snyk] Security upgrade showdown from 1.8.6 to 1.9.1 #37 from curbengh/globbing
1ddc395 refactor(test): dedup functions
c4b11ef refactor: set default config in main index.js
be910f3 fix: compatibility with non-globbing option
26ded4e feat: path globbing
25166f3 Merge pull request Weird behaviour when passing functions from helpers meteor/blaze#47 from curbengh/custom-options
c2a178f fix(eslint): specify .json file extension
64d15f6 style(eslint): should not override eslint-config-hexo
09cb6de feat: support Less.js options

Compare

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

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Snyk has created this PR to upgrade hexo-renderer-less from 0.1.3 to 2.0.2. See this package in npm: https://www.npmjs.com/package/hexo-renderer-less See this project in Snyk: https://app.snyk.io/org/ekmixon/project/cc54b2ec-5a5e-4872-8dc8-53ea03457adf?utm_source=github&utm_medium=upgrade-pr

pull-request-quantifier-deprecated · 2021-07-15T20:31:45Z

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.

pull-request-quantifier-deprecated bot added the Extra Small label Jul 15, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Snyk] Upgrade hexo-renderer-less from 0.1.3 to 2.0.2 #6

[Snyk] Upgrade hexo-renderer-less from 0.1.3 to 2.0.2 #6

snyk-bot commented Jul 15, 2021

Fix

FIx

Breaking changes

Features

Dependencies

Breaking changes

pull-request-quantifier-deprecated bot commented Jul 15, 2021

What can I do to optimize my changes

How to interpret the change counts in git diff output

[Snyk] Upgrade hexo-renderer-less from 0.1.3 to 2.0.2 #6

Are you sure you want to change the base?

[Snyk] Upgrade hexo-renderer-less from 0.1.3 to 2.0.2 #6

Conversation

snyk-bot commented Jul 15, 2021

Snyk has created this PR to upgrade hexo-renderer-less from 0.1.3 to 2.0.2.

Fix

FIx

Breaking changes

Features

Dependencies

Breaking changes

pull-request-quantifier-deprecated bot commented Jul 15, 2021

What can I do to optimize my changes

How to interpret the change counts in git diff output