README: state that dependency advisory/CVE coverage is out of scope - #43
Open
Kaushik2210 wants to merge 1 commit into
Open
Kaushik2210 wants to merge 1 commit into
Kaushik2210 wants to merge 1 commit into
Conversation
Nothing in the workflow fetches advisory data and hunters run with no external networking, so disclosed vulnerabilities in pinned dependencies are not found. The limit was implicit; a user evaluating the skill for dependency coverage only learned it from a 0% result. State it up front, alongside the existing needs_validation behavior for unobservable facts. Addresses gap 1 of cloudflare#20. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
Addresses gap 1 of #20 (the other gaps are design calls and are not touched here). Adds a short "Scope and limits" section to the README.
The limit is real but was implicit: no file in the workflow mentions advisory or CVE data (
grep -ri "advisor\|CVE"finds only the "known-vulnerable dependency is not a finding by itself" rule inSUPPLY-CHAIN-AND-RELEASE.md), and hunters run with no external networking. So a disclosed vulnerability in a pinned dependency that postdates the model's knowledge cannot be found, and someone evaluating the skill for that coverage only learns it from a 0% result.Change
README only, two bullets:
needs_validationwith the fact named (restating existing behavior from the design principles andATTACK-CLASSES.md).No behavior change. Happy to reword if the maintainers want a different framing.
🤖 Generated with Claude Code