Open dependabot[bot] opened 6 months ago
The following labels could not be found: vulnerabilites
.
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/jest-util@29.6.1, npm/js-yaml@4.1.0, npm/json-stringify-safe@5.0.1, npm/json5@2.2.3, npm/jsonfile@6.1.0, npm/jsonparse@1.3.1, npm/kind-of@6.0.3, npm/lerna@7.4.2, npm/make-fetch-happen@11.1.1, npm/merge2@1.4.1, npm/minimatch@3.1.2, npm/minimist@1.2.8, npm/minipass@4.2.8, npm/ms@2.1.2, npm/negotiator@0.6.3, npm/node-fetch@2.6.7, npm/normalize-package-data@3.0.3, npm/npm-registry-fetch@14.0.5, npm/npmlog@6.0.2, npm/nx-cloud@16.5.2, npm/nx@16.9.1, npm/object-assign@4.1.1, npm/once@1.4.0, npm/onetime@5.1.2, npm/p-limit@3.1.0, npm/p-map@4.0.0, npm/p-reduce@2.1.0, npm/parse-json@5.2.0, npm/path-key@3.1.1, npm/path-scurry@1.10.1, npm/picomatch@2.3.1, npm/prettier@2.8.8, npm/pretty-format@29.6.1, npm/protocols@2.0.1, npm/raw-body@2.5.1, npm/read-package-json@6.0.4, npm/readable-stream@3.6.2, npm/resolve@1.22.2, npm/retry@0.12.0, npm/rimraf@3.0.2, npm/safe-buffer@5.2.1, npm/safer-buffer@2.1.2, npm/semver@7.5.4, npm/signal-exit@3.0.7, npm/sigstore@1.7.0, npm/slash@3.0.0, npm/source-map@0.6.1, npm/string-width@4.2.3, npm/strip-ansi@6.0.1, npm/strong-log-transformer@2.1.0, npm/tar@6.1.11, npm/through@2.3.8, npm/ts-jest@29.1.1, npm/tslib@2.6.0, npm/tweetnacl@0.14.5, npm/type-check@0.4.0, npm/typescript@4.9.5, npm/unpipe@1.0.0, npm/util-deprecate@1.0.2, npm/validate-npm-package-license@3.0.4, npm/validate-npm-package-name@5.0.0, npm/wcwidth@1.0.1, npm/which@2.0.2, npm/xhr@2.6.0, npm/xtend@4.0.2, npm/yallist@4.0.0, npm/yargs-parser@20.2.4, npm/yargs@17.7.2
🚨 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 |
---|---|---|
Install scripts | npm/es5-ext@0.10.62 |
|
Protestware/Troll package | npm/es5-ext@0.10.62 |
|
Mild CVE | npm/es5-ext@0.10.62 |
|
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.
This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.
Consider that consuming this package my come along with functionality unrelated to its primary purpose.
Contains a low severity Common Vulnerability and Exposure (CVE).
Remove or replace dependencies that include known low severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
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.
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.
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/foo@1.0.0
or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore npm/es5-ext@0.10.62
Bumps ejs from 3.1.9 to 3.1.10.
Release notes
Sourced from ejs's releases.
Commits
d3f807d
Version 3.1.109ee26dd
Mocha TDDe469741
Basic pollution protection715e950
Merge pull request #756 from Jeffrey-mu/maincabe314
Include advanced usage examples29b076c
Added header11503c7
Merge branch 'main' of github.com:mde/ejs into main7690404
Added security banner to READMEf47d7ae
Update SECURITY.md828cea1
Update SECURITY.mdDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show