Skip to content

[LOW] Remove vulnerable docs preview dependencies - #1714

Merged
olleolleolle merged 2 commits into
lostisland:mainfrom
OskarEichler:codex/security-update-docs-cli
Sep 16, 2026
Merged

olleolleolle merged 2 commits into
lostisland:mainfrom
OskarEichler:codex/security-update-docs-cli

Conversation

@OskarEichler

Copy link
Copy Markdown
Contributor

Summary

Update the local documentation preview server from docsify-cli 4.4.4 to 5.0.0 and refresh its lockfile to remove the currently reported transitive advisories.

The old lock resolved 208 packages and npm audit reported nine advisories (seven moderate, two high), including marked regex denial of service and ws fragment-driven memory exhaustion. The refreshed graph contains 122 packages, pins the fixed ws 7.5.11, and reports zero known vulnerabilities.

Verification

  • npm ci --ignore-scripts: 122 packages installed from the refreshed lockfile.
  • npm audit: zero vulnerabilities.
  • npm run docs -- --port 4568: local preview server started successfully.
  • A bounded local curl smoke check retrieved the Faraday documentation page and expected title/core script.
  • Package-lock registry entries retain integrity metadata; git diff --check passes.

No production service, release workflow, or credential was used.

Scope and limitations

This tool is used only by the local npm run docs preview command and is not packaged in the Faraday gem or executed by CI/release workflows. The upstream 5.0.0 release was published on 2026-07-29, more than a month before this change.

Breaking-change notes

docsify-cli 5 requires Node.js >= 20.11.0. The verification used Node 22.23.2. Maintainers using an older Node release will need to upgrade Node to run the local docs preview command; gem consumers are unaffected.

@olleolleolle
olleolleolle merged commit d37e1e0 into lostisland:main Sep 16, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants