Repository navigation
fix(security): update vulnerable Markdown tooling and enforce audit - #34
Merged
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
Update markdownlint-cli2 0.24.0, brace-expansion5.0.12 and patched KaTeX0.18.2 override, with no vulnerability exception. Add all-severity npm audit and actual Markdown/math/TOML compatibility regression gates to existing CI; npm ci now ignores lifecycle scripts. Existing workflow permissions and scheduled issue reporter unchanged.
Validation
Fresh local install: npm audit zero vulnerabilities at all severities; compatibility smoke tests and repository Markdown lint pass. Exact final head94ecd410374ad26c4fbbf6316779656f510d542c hosted lint including new audit/regression gates passed. Spelling gate recognizes real package names.
Authorization and release impact
Previously blocked exact workflow edit explicitly approved and completed. No repository settings, permissions, exceptions or required checks changed. Development/CI tooling only; no tool release warranted.