[Chore] Update dependencies to latest ncu versions and clear npm audit findings
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 120
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Update npm dependencies to the latest versions reported by ncu at implementation time, and reduce npm audit vulnerabilities as far as is rational without risky breakage.
Details
Direct dependency is currently vitepress@^1.6.4. Run ncu during implementation and bump packages to the latest stable versions it reports.
Also address known transitive vulnerabilities (today: vite via vitepress, already partially mitigated with an esbuild override). Prefer npm overrides for patched transitive versions when a direct bump is not available, and follow .ai-tasks/update-deps-security-notes.md for the security review.
Scope:
- Update
package.json/package-lock.jsonviancu+npm install - Clear or reduce medium/high/critical
npm auditfindings where a safe override or upgrade exists - Do not chase low-severity noise or force major upgrades that break the docs site
- Keep VitePress build working (
npm run docs:build)
Out of scope:
- Content/documentation page edits
- Large refactors unrelated to dependency resolution
Checklist
- Run
ncuand update dependencies to the latest versions available at implementation time - Refresh the lockfile with
npm install - Apply rational fixes for medium/high/critical
npm auditfindings (overrides only when needed) - Follow
.ai-tasks/update-deps-security-notes.md(dependency diff, audit, suspicious packages/scripts, lockfile integrity, build smoke check) - Confirm
npm run docs:buildsucceeds - Summarize remaining vulnerabilities that cannot be fixed without breaking changes
Notes
PR will be linked here after creation.
Suggested PR title: Chore: Update dependencies and clear npm audit findings
Security review checklist reference: .ai-tasks/update-deps-security-notes.md
Verification
ncureports no remaining outdated direct dependencies (or remaining gaps are documented)npm audithas no unresolved medium/high/critical issues that can be fixed rationallynpm run docs:buildcompletes without errors- Security notes checklist items are covered in the PR description
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with package.json, package-lock.json, and .ai-tasks/update-deps-security-notes.md. Run ncu, npm install, and npm audit to identify updates and rational security fixes, then verify npm run docs:build. Done means safe medium/high/critical findings are addressed or documented, the lockfile and security notes are refreshed, and the build succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100