Skip to content
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

Expecting a new release from develop branch to resolve marked dependency vulnerabilities #2372

Closed
1 task
somnathpathak opened this issue Feb 15, 2024 · 2 comments

Comments

@somnathpathak
Copy link

Bug Report

Steps to reproduce

npm install docsify
npm audit

Current behaviour

Bump the marked devDependency to 4.2.12 in new release

Expected behaviour

Currently, marked is at 1.2.9 which results in following vulnerabilities:

Other relevant information

  • Docsify version: 4.13.1
  • Bug still occurs when all/other plugins are disabled?

  • Docsify plugins (if the bug happens when plugins enabled, please try to isolate the issue):

Please create a reproducible sandbox

Edit 307qqv236

Mention the docsify version in which this bug was not present (if any)

develop branch. NOT YET RELEASED.

@somnathpathak
Copy link
Author

@jhildenbiddle @QingWei-Li Could you please look into this.

@trusktr
Copy link
Member

trusktr commented Feb 15, 2024

Hi, thanks for getting involved!

Its nice to be up to date with libraries, but if you had an issue with this, you can easily change the offending markup in your markdown.

It would be far more valuable to know what problem you specifically face, if anything, rather than just assuming that posting npm audit results is always meaningful.

We will release when ready.

In the meantime, if you have an actual problem with a piece of markdown, please open another issue.

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

No branches or pull requests

2 participants