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
The new 2.0.0-rc.6 tag was pushed but the npm package.json was not updated. Need to bump the version so that the new version can be published to npm. This is necessary for validating 2.0 against existing plugin packages (plugins have a peer dependency back to the host @finos/git-proxy package).
Also added version bumps via npm audit fix. If someting breaks, I'll revert those changes. There were some high and medium sev vulns in a few packages (frontend mostly?).
$ npm audit
# npm audit report
axios <=1.14.0
Severity: critical
Axios has a NO_PROXY Hostname Normalization Bypass Leads to SSRF - https://github.com/advisories/GHSA-3p68-rc4w-qgx5
Axios has Unrestricted Cloud Metadata Exfiltration via Header Injection Chain - https://github.com/advisories/GHSA-fvcv-3m26-pcqx
fix available via `npm audit fix`
node_modules/axios
brace-expansion <1.1.13 || >=2.0.0 <2.0.3
Severity: moderate
brace-expansion: Zero-step sequence causes process hang and memory exhaustion - https://github.com/advisories/GHSA-f886-m6hf-6m8v
brace-expansion: Zero-step sequence causes process hang and memory exhaustion - https://github.com/advisories/GHSA-f886-m6hf-6m8v
fix available via `npm audit fix`
node_modules/@npmcli/map-workspaces/node_modules/brace-expansion
node_modules/@typescript-eslint/typescript-estree/node_modules/brace-expansion
node_modules/@vitest/coverage-v8/node_modules/brace-expansion
node_modules/brace-expansion
node_modules/glob/node_modules/brace-expansion
fast-xml-parser 5.0.0 - 5.5.6
Severity: moderate
Entity Expansion Limits Bypassed When Set to Zero Due to JavaScript Falsy Evaluation in fast-xml-parser - https://github.com/advisories/GHSA-jp2q-39xq-3w4g
fix available via `npm audit fix`
node_modules/fast-xml-parser
@aws-sdk/xml-builder 3.894.0 - 3.972.14
Depends on vulnerable versions of fast-xml-parser
node_modules/@aws-sdk/xml-builder
flatted <=3.4.1
Severity: high
Prototype Pollution via parse() in NodeJS flatted - https://github.com/advisories/GHSA-rf6f-7fwh-wjgh
fix available via `npm audit fix`
node_modules/flatted
follow-redirects <=1.15.11
Severity: moderate
follow-redirects leaks Custom Authentication Headers to Cross-Domain Redirect Targets - https://github.com/advisories/GHSA-r4q5-vmmm-2653
fix available via `npm audit fix`
node_modules/follow-redirects
lodash <=4.17.23
Severity: high
lodash vulnerable to Code Injection via `_.template` imports key names - https://github.com/advisories/GHSA-r5fr-rjxr-66jc
lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit` - https://github.com/advisories/GHSA-f23m-r3pf-42rh
fix available via `npm audit fix`
node_modules/lodash
path-to-regexp 8.0.0 - 8.3.0
Severity: high
path-to-regexp vulnerable to Denial of Service via sequential optional groups - https://github.com/advisories/GHSA-j3q9-mxjg-w52f
path-to-regexp vulnerable to Regular Expression Denial of Service via multiple wildcards - https://github.com/advisories/GHSA-27v5-c462-wpq7
fix available via `npm audit fix`
node_modules/path-to-regexp
picomatch <=2.3.1 || 4.0.0 - 4.0.3
Severity: high
Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching - https://github.com/advisories/GHSA-3v7f-55p6-f55p
Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching - https://github.com/advisories/GHSA-3v7f-55p6-f55p
Picomatch has a ReDoS vulnerability via extglob quantifiers - https://github.com/advisories/GHSA-c2c7-rcm5-vvqj
Picomatch has a ReDoS vulnerability via extglob quantifiers - https://github.com/advisories/GHSA-c2c7-rcm5-vvqj
fix available via `npm audit fix`
node_modules/picomatch
node_modules/tinyglobby/node_modules/picomatch
node_modules/vite/node_modules/picomatch
node_modules/vitest/node_modules/picomatch
vite 7.0.0 - 7.3.1
Severity: high
Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling - https://github.com/advisories/GHSA-4w7w-66w2-5vf9
Vite: `server.fs.deny` bypassed with queries - https://github.com/advisories/GHSA-v2wj-q39q-566r
Vite Vulnerable to Arbitrary File Read via Vite Dev Server WebSocket - https://github.com/advisories/GHSA-p9ff-h696-f583
fix available via `npm audit fix`
node_modules/vite
yaml 2.0.0 - 2.8.2
Severity: moderate
yaml is vulnerable to Stack Overflow via deeply nested YAML collections - https://github.com/advisories/GHSA-48c2-rrv3-qjmp
fix available via `npm audit fix`
node_modules/yaml
11 vulnerabilities (5 moderate, 5 high, 1 critical)
To address all issues, run:
npm audit fix
$ npm audit fix
changed 24 packages, and audited 1184 packages in 7s
274 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.
Snapshot Warnings
⚠️: No snapshots were found for the head SHA af3c45f.
Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.
This change is blocked by failures in git-proxy-cli. That package depends on rc.5. Bumping the root package to rc.6 prevents a successful npm install. This may be due to the fact that npm workspaces cannot handle intra-workspace dependencies cleanly or that the root of the workspace itself is the dependency. I frankly don't know if this is a supported configuration for the project build/structure. Yarn or pnpm would be better suited for this.
21 verbose stack at async Arborist.reify (/home/tom/.local/share/mise/installs/node/22.14.0/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:131:5)
21 verbose stack at async Install.exec (/home/tom/.local/share/mise/installs/node/22.14.0/lib/node_modules/npm/lib/commands/install.js:150:5)
21 verbose stack at async Npm.exec (/home/tom/.local/share/mise/installs/node/22.14.0/lib/node_modules/npm/lib/npm.js:207:9)
22 error code ETARGET
23 error notarget No matching version found for @finos/git-proxy@2.0.0-rc.6.
24 error notarget In most cases you or one of your dependencies are requesting
24 error notarget a package version that doesn't exist.
25 silly unfinished npm timer reify 1776257027390
26 silly unfinished npm timer reify:loadTrees 1776257027391
27 verbose cwd /home/tom/repos/git-proxy
28 verbose os Linux 6.19.8-100.fc42.x86_64
29 verbose node v22.14.0
30 verbose npm v10.9.2
31 verbose exit 1
32 verbose code 1
33 error A complete log of this run can be found in: /home/tom/.npm/_logs/2026-04-15T12_43_47_258Z-debug-0.log
The syncpack tool can be used to sync other package versions as well, we just limit it to the @finos packages to use it for that purpose. Perhaps overkill for this, but thought I'd mention it in case it help automate something here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The new 2.0.0-rc.6 tag was pushed but the npm package.json was not updated. Need to bump the version so that the new version can be published to npm. This is necessary for validating 2.0 against existing plugin packages (plugins have a peer dependency back to the host
@finos/git-proxypackage).Also added version bumps via
npm audit fix. If someting breaks, I'll revert those changes. There were some high and medium sev vulns in a few packages (frontend mostly?).