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

use the latest version for component : v8:5.5.5 #1548

Closed
anurag92dash opened this issue Apr 24, 2024 · 3 comments
Closed

use the latest version for component : v8:5.5.5 #1548

anurag92dash opened this issue Apr 24, 2024 · 3 comments
Labels
🦄 Feature Request [ISSUE] Suggestion for new feature, update or change 🕸️ Inactive 🛑 No Response [ISSUE] Response was requested, but has not been provided

Comments

@anurag92dash
Copy link

Is your feature request related to a problem? If so, please describe.

my organization has security vulnerability tests before I deploy an opensource software.
while scanning dashy image, it was recommended to use the latest version for v8:5.5.5 --> 12.1.285.24
Can you please help me upgrade this component.

Describe the solution you'd like

update the Component: v8:5.5.5 -> to latest version 12.1.285.24

Priority

Medium (Would be very useful)

Is this something you would be keen to implement

Yes!

@anurag92dash anurag92dash added the 🦄 Feature Request [ISSUE] Suggestion for new feature, update or change label Apr 24, 2024
@liss-bot
Copy link
Collaborator

If you're enjoying Dashy, consider dropping us a ⭐
🤖 I'm a bot, and this message was automated

@Lissy93
Copy link
Owner

Lissy93 commented May 11, 2024

update the Component: v8:5.5.5 -> to latest version 12.1.285.24

Which library? (Component isn't included in Dashy).

Re the package vulnerabilities, I have gone through each and ensured none of them are actually exploitable vulnerabilities. Course most Node.js projects will have some kind of output from npm audit, and it looks scarier than it is.

But I also totally understand that many orgs don't let you deploy anything which includes a known vulnerbale package.

@CrazyWolf13 CrazyWolf13 added 🚏 Awaiting User Response [ISSUE] Response from original author is pending 🛑 No Response [ISSUE] Response was requested, but has not been provided labels May 16, 2024
@liss-bot
Copy link
Collaborator

Issue closed due to no response from user.

@liss-bot liss-bot removed the 🚏 Awaiting User Response [ISSUE] Response from original author is pending label May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🦄 Feature Request [ISSUE] Suggestion for new feature, update or change 🕸️ Inactive 🛑 No Response [ISSUE] Response was requested, but has not been provided
Projects
None yet
Development

No branches or pull requests

4 participants