Skip to content

[Snyk] Upgrade @contentstack/cli-command from 1.7.0 to 1.7.1#450

Open
alokshukla2012 wants to merge 1 commit intomainfrom
snyk-upgrade-a2e621478b55b83ab292a8f37ccf0f2a
Open

[Snyk] Upgrade @contentstack/cli-command from 1.7.0 to 1.7.1#450
alokshukla2012 wants to merge 1 commit intomainfrom
snyk-upgrade-a2e621478b55b83ab292a8f37ccf0f2a

Conversation

@alokshukla2012
Copy link

snyk-top-banner

Snyk has created this PR to upgrade @contentstack/cli-command from 1.7.0 to 1.7.1.

ℹ️ 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.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released 22 days ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
87 No Known Exploit
Release notes
Package name: @contentstack/cli-command
  • 1.7.1 - 2026-01-12

    Merge pull request #790 from contentstack/hotfix/missing-oclif-core-d…

    …ependency

    Hotfix/missing oclif core dependency

  • 1.7.0 - 2025-12-09

    Merge pull request #783 from contentstack/fix/package-lock-file-branches

    fix lock file branches release

from @contentstack/cli-command GitHub release notes

Important

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

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:

Snyk has created this PR to upgrade @contentstack/cli-command from 1.7.0 to 1.7.1.

See this package in npm:
@contentstack/cli-command

See this project in Snyk:
https://app.snyk.io/org/contentstack-devex/project/867008ba-2013-42f6-a7b0-589cb3379a47?utm_source=github&utm_medium=referral&page=upgrade-pr
@alokshukla2012 alokshukla2012 requested a review from a team as a code owner February 3, 2026 08:22
@github-actions
Copy link

github-actions bot commented Feb 3, 2026

Coverage report for commit: 9bb08b8
File: coverage/clover.xml

Cover ┌─────────────────────────┐ Freq.
   0% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  10% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  20% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  30% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  40% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  50% │ ░░░░░░░░░░░░░░░░░░░░░░░ │  0.0%
  60% │ ███░░░░░░░░░░░░░░░░░░░░ │  4.2%
  70% │ █████████░░░░░░░░░░░░░░ │ 16.7%
  80% │ █████████░░░░░░░░░░░░░░ │ 16.7%
  90% │ █████████░░░░░░░░░░░░░░ │ 16.7%
 100% │ ███████████████████████ │ 45.8%
      └─────────────────────────┘
 *Legend:* █ = Current Distribution 
Summary - Lines: 79.58% | Methods: 76.13% | Branches: 56.94%
FilesLinesMethodsBranches
src
   app-cli-base-command.ts80.00%100.00%50.00%
   base-command.ts80.00%80.00%46.88%
src/commands/app
   create.ts83.11%95.00%67.44%
   delete.ts87.50%100.00%73.47%
   deploy.ts62.79%70.00%50.55%
   get.ts100.00%100.00%74.07%
   index.ts66.67%--
   install.ts90.00%100.00%57.80%
   reinstall.ts90.24%100.00%57.02%
   uninstall.ts100.00%100.00%63.41%
   update.ts71.05%50.00%75.76%
src/config
   index.ts100.00%100.00%100.00%
src/factories
   uninstall-app-factory.ts100.00%100.00%100.00%
src/graphql
   queries.ts100.00%100.00%100.00%
src/messages
   index.ts100.00%100.00%50.00%
src/strategies
   uninstall-all.ts100.00%100.00%100.00%
   uninstall-selected.ts91.67%100.00%50.00%
src/types
   app.ts100.00%100.00%100.00%
   index.ts100.00%100.00%100.00%
src/util
   common-utils.ts69.93%61.29%27.35%
   fs.ts95.24%100.00%83.33%
   index.ts100.00%100.00%100.00%
   inquirer.ts77.40%75.00%57.55%
   log.ts71.93%66.67%48.15%

🤖 comment via lucassabreu/comment-coverage-clover

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants