microsoft / microsoft/onnxruntime
[Feature Request] NodeJS dependency hygiene
- Dominant language
- C++
- Stars
- 21.9k
- Forks
- 4.2k
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 184
Description
### Describe the feature request
Please consider
1. Doing an audit pass on the Nodejs dependencies to only have maintained dependencies. Looking at https://github.com/microsoft/onnxruntime/blob/main/js/node/package.json anecdotally, I noticed jsonc was last published 7 years ago and it hasn't been keeping up even with its own dependency updates. Having unmaintained dependencies creates risks including potential unpatched security volunerabilities.
2. Adding Dependabot updates with automerge with full CI for Nodejs dependencies, to improve patching response time. As an example, the recent adm-zip security update took three weeks to get picked up here in onnxruntime. (Ref: https://github.com/microsoft/onnxruntime/commit/00e575d51c123a5b618c77fbb4681ffb04cf8697 on 7/30/2026 and https://github.com/cthackers/adm-zip/releases v0.6.0 released on 7/10/2026).
Thank you!
### Describe scenario use case
Using nodejs onnx runtime in general.
Contributor guide
Research direction
Start with js/node/package.json and audit the listed Node.js dependencies for maintenance and security status, including jsonc and adm-zip. Then review how dependency updates and CI are configured in the repository. Done means the dependency set and update process address the request, with Dependabot automation, automerge, and full Node.js CI coverage defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- ci-cd, devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100