Moe BenSu

@VictorCazanave > My initial plan was to keep the same components (hoping they would be compatible with Vue 3) and update the wrapper to support both Vue 2 and Vue...

@apertureless I can help. However, is there somebody who's been already working on it? OR do you have some thoughts about how you would prefer to go about it?

@Barqawiz I guess, this is really a nice to have for easier usage. You can assign me to it, if you still want it.

@malekim first of all, thanks for the work your pulling off here. I wanna ask, if you could give an update about the progress status of including vue 3 support?

@LauBeck were you able to make the plugin compatible with Vue 3 or have you maybe found any other good alternatives?

@sagikazarmark When running i.e. `trivy image -v dexidp/dex:latest-alpine` it reports as well **old** CRITICAL CVEs that should be already fixed in the past, but for some reason trivy reports them...

@sagikazarmark `trivy image -d dexidp/dex:latest-alpine` yields this output ```bash ... 2025-04-23T09:22:42+02:00 DEBUG [secret] No secret config detected config_path="trivy-secret.yaml" 2025-04-23T09:22:42+02:00 DEBUG [nuget] The nuget packages directory couldn't be found. License search...

@sagikazarmark I got same output with a tagged version 

@sagikazarmark No. Those are the outputs with the new trivy. `trivy image -d dexidp/dex:latest-alpine` ```bash 2025-04-23T15:00:54+02:00 DEBUG [image] Detected image ID image_id="sha256:f8142d6c3f886a180ca1b9b7f6e6d420b484051a2aeb5be2c76f142515cba3ff" 2025-04-23T15:00:54+02:00 DEBUG [image] Detected diff ID diff_ids=[sha256:08000c18d16dadf9553d747a58cf44023423a9ab010aab96cf263d2216b8b350 sha256:ba8d3e2b323ce43e9ec8ef16293e98d3db8200d2636d1904ebfbadcab940555e...

@nabokihms I put something together. PR should be ready for review.