Security Vulnerabilities Detected by Dependabot (postgreSQL/html/jquery.js) · Issue #161 · EDIorg/ecocomDP · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dependabot has flagged the ecocomDP repository for potential security vulnerabilities related to the file postgreSQL/html/jquery.js. This file appears to have been originally committed by you.
There are a couple ways we could address these reported vulnerabilities:
Update the files: Investigate the specific vulnerabilities reported by Dependabot and update the affected files (or their dependencies) to resolve these issues. This would preserve any potential utility of this content.
Remove the files: If the content in these files is no longer deemed necessary or if updating them is not feasible, we could remove them from the repository entirely.
What are your thoughts on how we should proceed with this?
Thanks for your input!
The text was updated successfully, but these errors were encountered:
I don't think updating is worth the time. It (along with the HTML) was created by the program that generated ERD (in this case, schemaSpy), and no one uses the html view. We do use the SVG output, but have been editing that manually.
I'll drop the text of this file but leave a note there that says it that if someone wants to regenerate the html and svg, they should do so with a current version of schemaSpy or some other ERD generator.
@mobb, it looks like Dependabot isn't entirely happy with this. Even though you've commented out the code, Dependabot still flags it. One option might be to update the version number in jquery.js to the one it recommends.
Hi @mobb,
Dependabot has flagged the ecocomDP repository for potential security vulnerabilities related to the file
postgreSQL/html/jquery.js
. This file appears to have been originally committed by you.There are a couple ways we could address these reported vulnerabilities:
What are your thoughts on how we should proceed with this?
Thanks for your input!
The text was updated successfully, but these errors were encountered: