Closed btmnk closed 2 years ago
Hey there,
you're right, we should clean up and update the boilerplate. We're currently a little bit short handed and will try to get tp this asap.
Thank you, for the input.
Cheers, Paul
Acting on behalf of Daimler TSS GmbH.
Message to comment on stale issues. If none provided, will not mark issues stale
Sorry if those are not supposed to be reported here but I wasn't sure how to submit dependency vulnerabilities with the provided policy (https://www.daimler.com/whitehat/) since these vulnerabilities are not really security relevant since they only affect dev-dependencies.
I did a fresh install of the boilerplate an ran
yarn audit
and got these results:After updating the following packages I was able to reduce the vulnerabilities to 2:
This requires to adjust some of the build configurations and I have still some issues with url-search-params and cjs but I think generally updating the packages to their latest major version is a good thing. There are many other packages who have already at least 1-2 new major versions as well.
The remaining vulnerabilities were these:
Not even sure if we need postcss-remove-prefixes but optimize-css-assets-webpack-plugin for example is deprecated for webpack 5 since webpack has it's own minimizer now (https://github.com/webpack-contrib/css-minimizer-webpack-plugin).
I know these vulnerabilities are just dev-dependencies and are not production-critical but I think they unnecessarily clutter reports such as blackduck scans and make it harder to identify actual production critical vulnerabilities.