Chris Adams
Chris Adams
The WASM toolchain offers some interesting performance benefits but it definitely adds complexity: https://github.com/LibraryOfCongress/bagger-js/pull/48/commits/e273bdeb4bc21e4124007e9a87baf0ad3d1591c0 https://github.com/acdha/wasm-hashing/commit/673e09b2c6454bf9425e0350a0a071ce19a524ce
@eikeon Mostly leaving this here as a place to collect our discussion notes but perhaps e.g. @edsu, @dbrunton, @kzwa will be able to contribute some integration examples beyond the ones...
@dependabot recreate
@dependabot recreate
@dependabot rebase
@dbrunton We might want to consider how necessary the various levels of UI in this issue are for 1.0 – perhaps we simply have an overwrite allow/deny toggle and good...
Thanks - I understand it’s a non-trivial decision.
We use things like Terraform modules which have embedded examples which Trivy will flag as security issues even though they're not used or referenced by our code in any way....
It no longer reproduces _but_ I noticed something interesting when running pre-commit with a clean cache: ``` [INFO] Initializing environment for https://github.com/abravalheri/validate-pyproject. [INFO] Initializing environment for https://github.com/abravalheri/validate-pyproject:.[all]. ``` That happens...
I strongly agree with the decision to upgrade to log4j 2. I had a partial branch in progress but ran out of time to work on it and ended up...