[Snyk] Security upgrade @11ty/eleventy-img from 3.0.0 to 6.0.0

[kingjay66]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	631

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@11ty/[email protected] 🔁 npm/@11ty/[email protected]	environment Transitive: eval, network, shell	+45	182 MB	zachleat

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	package-lock.json package.json	🚫
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	package-lock.json package.json	🚫
Filesystem access	npm/@netlify/[email protected]	Module: fs Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: npm_config_build_from_source Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: npm_package_config_libvips Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/[email protected]	Location: Package overview	package-lock.json package.json	🚫
Dynamic require	npm/[email protected]	Location: Package overview	package-lock.json package.json	🚫
Dynamic require	npm/[email protected]	Location: Package overview	package-lock.json package.json	🚫
Dynamic require	npm/[email protected]	Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: PKG_CONFIG_PATH Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: SHARP_IGNORE_GLOBAL_LIBVIPS Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: SHARP_FORCE_GLOBAL_LIBVIPS Location: Package overview	package-lock.json package.json	🚫
Dynamic require	npm/[email protected]	Location: Package overview	package-lock.json package.json	🚫
Dynamic require	npm/[email protected]	Location: Package overview	package-lock.json package.json	🚫
Dynamic require	npm/[email protected]	Location: Package overview	package-lock.json package.json	🚫
Dynamic require	npm/[email protected]	Location: Package overview	package-lock.json package.json	🚫
Install scripts	npm/[email protected]	Install script: install Source: node install/check	package-lock.json package.json	🚫
Uses eval	npm/@emnapi/[email protected]	Eval Type: Function Location: Package overview	package-lock.json package.json	🚫
Uses eval	npm/@emnapi/[email protected]	Eval Type: Function Location: Package overview	package-lock.json package.json	🚫
Dynamic require	npm/@emnapi/[email protected]	Location: Package overview	package-lock.json package.json	🚫
Uses eval	npm/@emnapi/[email protected]	Eval Type: Function Location: Package overview	package-lock.json package.json	🚫
Uses eval	npm/@emnapi/[email protected]	Eval Type: Function Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/@emnapi/[email protected]	Env Vars: NODE_ENV Location: Package overview	package-lock.json package.json	🚫
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/@11ty/[email protected]	Env Vars: ELEVENTY_RUN_MODE Location: Package overview	package-lock.json package.json	🚫
Environment variable access	npm/@11ty/[email protected]	Env Vars: ELEVENTY_RUN_MODE Location: Package overview	package-lock.json package.json	🚫

View full report↗︎

Next steps

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

What is dynamic require?

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code.

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

What is dynamic code execution?

Package uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@netlify/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@emnapi/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@11ty/[email protected]