-
Notifications
You must be signed in to change notification settings - Fork 4
build(deps): bump tmp and @nestjs/cli #230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Removes [tmp](https://github.com/raszi/node-tmp). It's no longer used after updating ancestor dependency [@nestjs/cli](https://github.com/nestjs/nest-cli). These dependencies need to be updated together. Removes `tmp` Updates `@nestjs/cli` from 7.6.0 to 11.0.10 - [Release notes](https://github.com/nestjs/nest-cli/releases) - [Changelog](https://github.com/nestjs/nest-cli/blob/master/.release-it.json) - [Commits](nestjs/nest-cli@7.6.0...11.0.10) --- updated-dependencies: - dependency-name: tmp dependency-version: dependency-type: indirect - dependency-name: "@nestjs/cli" dependency-version: 11.0.10 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>
⛔ Snyk checks have failed. 5 issues have been found so far.
⛔ security/snyk check is complete. 5 issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) 💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Semgrep found 1 Risk: Affected versions of jsonwebtoken are vulnerable to Improper Authentication. Insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC. Manual Review Advice: A vulnerability from this advisory is reachable if you are using a poorly implemented key retrieval function and your application is supporting usage of both symmetric key and asymmetric key in Fix: Upgrade this library to at least version 9.0.0 at brokencrystals/package-lock.json:11412. Reference(s): GHSA-hjrf-2m68-5959, CVE-2022-23541 Semgrep found 1 Risk: Affected versions of jsonwebtoken are vulnerable to Use Of A Broken Or Risky Cryptographic Algorithm. The library could be misconfigured so that legacy, insecure key types are used for signature verification. For example, DSA keys could be used with the RS256 algorithm. Manual Review Advice: A vulnerability from this advisory is reachable if you are using a legacy, insecure key type with a supported algorithm; for example, DSA keys could be used with the RS256 algorithm Fix: Upgrade this library to at least version 9.0.0 at brokencrystals/package-lock.json:11412. Reference(s): GHSA-8cf7-32gw-wr33, CVE-2022-23539 |
Semgrep found 1 Risk: Affected versions of jsonwebtoken are vulnerable to Improper Authentication. Insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC. Manual Review Advice: A vulnerability from this advisory is reachable if you are using a poorly implemented key retrieval function and your application is supporting usage of both symmetric key and asymmetric key in Fix: Upgrade this library to at least version 9.0.0 at brokencrystals/package-lock.json:11412. Reference(s): GHSA-hjrf-2m68-5959, CVE-2022-23541 Semgrep found 1 Risk: Affected versions of jsonwebtoken are vulnerable to Use Of A Broken Or Risky Cryptographic Algorithm. The library could be misconfigured so that legacy, insecure key types are used for signature verification. For example, DSA keys could be used with the RS256 algorithm. Manual Review Advice: A vulnerability from this advisory is reachable if you are using a legacy, insecure key type with a supported algorithm; for example, DSA keys could be used with the RS256 algorithm Fix: Upgrade this library to at least version 9.0.0 at brokencrystals/package-lock.json:11412. Reference(s): GHSA-8cf7-32gw-wr33, CVE-2022-23539 |
New Issues (2)Checkmarx found the following issues in this Pull Request
Fixed Issues (10)Great job! The following issues were fixed in this Pull Request
|
Removes tmp. It's no longer used after updating ancestor dependency @nestjs/cli. These dependencies need to be updated together.
Removes
tmp
Updates
@nestjs/cli
from 7.6.0 to 11.0.10Release notes
Sourced from
@nestjs/cli
's releases.... (truncated)
Commits
e47541d
chore(): release v11.0.103186552
Merge pull request #3115 from nestjs/revert-3047-renovate/major-angular-cli-m...ce6acd3
Revert "fix(deps): update angular-cli monorepo to v20 (major)"79ac1e2
Merge pull request #3114 from nestjs/revert-3109-chore/disable-shell-by-defaultd43b91c
Revert "chore: disable shell by default"fe3aca7
chore(): release v11.0.90594cb1
Merge pull request #3047 from nestjs/renovate/major-angular-cli-monorepo5bbd8f8
fix(deps): update angular-cli monorepo to v204434eb5
Merge pull request #3109 from nestjs/chore/disable-shell-by-defaultaa6f234
Merge pull request #3105 from nestjs/renovate/inquirer-prompts-7.xDependabot 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 <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.