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

Audit Report Issue due to 'marked' dependency #542

Open
FBNitro opened this issue Apr 11, 2019 · 4 comments
Open

Audit Report Issue due to 'marked' dependency #542

FBNitro opened this issue Apr 11, 2019 · 4 comments

Comments

@FBNitro
Copy link

FBNitro commented Apr 11, 2019

Both esdoc and esdoc-publish-html-plugin depend on 'marked', which has a security warning in the npm audit report.

Please upgrade to >=0.6.2 of marked to resolve this audit failure.
See: https://nodesecurity.io/advisories/812 for more information

npm audit --registry https://registry.npmjs.org

                       === npm audit security report ===


                                 Manual Review
             Some vulnerabilities require your attention to resolve

          Visit https://go.npm.me/audit-guide for additional guidance


  Moderate        Regular Expression Denial of Service

  Package         marked

  Patched in      >=0.6.2

  Dependency of   esdoc [dev]

  Path            esdoc > marked

  More info       https://nodesecurity.io/advisories/812


  Moderate        Regular Expression Denial of Service

  Package         marked

  Patched in      >=0.6.2

  Dependency of   esdoc-standard-plugin [dev]

  Path            esdoc-standard-plugin > esdoc-publish-html-plugin > marked

  More info       https://nodesecurity.io/advisories/812

found 2 moderate severity vulnerabilities in 859520 scanned packages
  2 vulnerabilities require manual review. See the full report for details.
@zachawilson
Copy link

Check #543

@Sonictherocketman
Copy link

+1

@csimi
Copy link

csimi commented Apr 29, 2019

Other than that it seems that all dependencies are locked to a single version which makes deduplication a no-go.
Also, if a vulnerability is found in any other dependency it's impossible to npm audit fix it automatically.

@gomesalexandre
Copy link

The author of the package seems mostly inactive, I'd suggest using a fork directly from GitHub in the meantime

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

5 participants