Skip to content

[Snyk] Fix for 2 vulnerabilities #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
patinthehat wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Fix for 2 vulnerabilities #24

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@
"@semantic-release/changelog": "^3.0.2",
"@semantic-release/commit-analyzer": "^6.1.0",
"@semantic-release/git": "^7.0.8",
"@semantic-release/npm": "^5.1.8",
"@semantic-release/npm": "^7.1.0",
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Feb 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Regenerate lockfile after dependency bumps

This change updates dependency ranges in package.json, but package-lock.json still resolves the old versions (@semantic-release/npm is still 5.3.5 at package-lock.json:1331 and eslint is still 6.8.0 at package-lock.json:4225). In any lockfile-based install path (for example npm ci or scanners that read the lockfile), the old vulnerable packages remain in use, so the intended security remediation is not actually applied.

Useful? React with 👍 / 👎.

"@semantic-release/release-notes-generator": "^7.1.4",
"@types/fs-extra": "^5.1.0",
"@types/lodash": "^4.14.132",
Expand All @@ -94,7 +94,7 @@
"conventional-changelog": "^3.1.3",
"conventional-changelog-cli": "^2.1.0",
"esbuild": "^0.8.39",
"eslint": "^6.6.0",
"eslint": "^9.0.0",
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Feb 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep ESLint major version compatible with Node 10 CI

The repository’s CI config runs linting on Node.js 10 (.travis.yml lines 2 and 12), but this change upgrades ESLint to ^9.0.0, which targets much newer Node runtimes; that makes the lint stage fail in the current CI environment. Unless the CI Node version is upgraded alongside this change, this dependency bump will block lint/test pipelines.

Useful? React with 👍 / 👎.

"eslint-plugin-import": "^2.18.2",
"eslint-plugin-jsdoc": "^17.1.1",
"eslint-plugin-no-null": "^1.0.2",
Expand Down