fix(deps): ignore unreachable ip-address advisory in dependabot config - #66
Merged
Merged
Conversation
Dependabot's daily Security job has failed identically since at least 2026-08-04 (security_update_not_possible: latest-resolvable-version 10.2.0, lowest-non-vulnerable-version 10.3.1). Traced why: ip-address isn't a direct dependency anywhere — it's nested 3 deep via @semantic-release/npm -> npm (bundled) -> socks -> ip-address@10.2.0. npm's published package ships bundleDependencies covering its entire tree, so it's vendored/pre-resolved at publish time. Verified empirically that a package.json `overrides` pin has zero effect on this path — node_modules/npm/node_modules/ip-address stayed at 10.2.0 after npm install with the override in place. No dependency management in this repo can reach it; only a new npm release bundling a patched socks/ip-address closes this. Ignoring it in dependabot.yml (with a dated comment explaining why + how to revisit) so the doomed daily retry stops failing CI. The underlying GHSA alert stays open/visible on the repo's Security tab — this only stops the unreachable PR-open attempt, not the vulnerability tracking itself. A permanently-red scheduled job trains people to stop looking at it, which risks masking a real, fixable advisory later.
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
1 participant
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.
Summary
Dependabot's daily Security job fails identically every day (
security_update_not_possible,latest-resolvable-version: 10.2.0,lowest-non-vulnerable-version: 10.3.1) becauseip-addressisn't a direct dependency anywhere — it's nested 3 deep:@semantic-release/npm→npm(bundled) →socks→ip-address@10.2.0.Why this can't be fixed with a manifest change
npm's published package shipsbundleDependenciescovering its entire tree, so it's vendored/pre-resolved at publish time — not resolved through the consuming project's normal dependency graph. Verified empirically: added apackage.jsonoverridespin forip-address >=10.3.1, rannpm install, andnode_modules/npm/node_modules/ip-addressstayed at10.2.0. No dependency-management mechanism available in this repo can reach it. Only a futurenpmrelease bundling a patchedsocks/ip-addresscloses this.Change
Adds an
ignorerule forip-addressin.github/dependabot.yml, with a dated comment explaining the full chain and how to revisit later. This stops the doomed daily retry from failing CI — it does not dismiss the underlying GHSA alert, which stays open/visible on the repo's Security > Dependabot alerts tab as it should.Why bother at all (low severity, so why not just leave it red?)
A permanently-red scheduled job trains people to stop looking at it, which risks masking an unrelated, actually-fixable advisory landing later in the same daily run. Silencing the unreachable one keeps the signal meaningful.
Pilot fix for this specific advisory — same root cause confirmed across 6 more repos on the shared node-*-mcp dependabot template (node-halopsa, node-superops, node-atera, node-syncro, node-connectwise-automate, node-it-glue); will propagate once this is verified.
🤖 Generated with murph