Every applicability statement published about this vulnerability, kept as each source wrote it rather than merged into one verdict. Where sources disagree, both positions are shown.
A statement that names no version covers the whole product, which is not the same as your version falling inside a range. Orderings marked best effort come from schemes with no published comparison algorithm; exact ones follow a published specification.
Precedence decides which claim wins when two sources describe the same product over the same version range. It is a property of the source, not of the claim, and changing it re-ranks the data without re-reading a single document.
| Product | Status | Versions | Remediation | Source | |
|---|---|---|---|---|---|
| https://github.com/tj-actions/changed-files | affected | >= eef94236f6b9dec768f89dc72b9e0b64e13bb36e, < ed68ef82c095e0d48ec87eccea555d944a631a4c | vendor fix → ed68ef82c095e0d48ec87eccea555d944a631a4c | osv | |
| tj-actions/changed-files | affected | < 46.0.1 | vendor fix → 46.0.1 | osv GHSA-mrrh-fwg8-r2c3 | |
| https://github.com/tj-actions/changed-files | fixed | ed68ef82c095e0d48ec87eccea555d944a631a4c | vendor fix → ed68ef82c095e0d48ec87eccea555d944a631a4c | osv | |
| tj-actions/changed-files | fixed | 46.0.1 | vendor fix → 46.0.1 | osv GHSA-mrrh-fwg8-r2c3 | |
| tj-actions/changed-files tj-actions · changed-files | affected | >= 1, < 46 | none available | cve_cna |
A claim with no version range is shown as written rather than expanded: a government catalog naming only a vendor and product is a real statement at zero granularity, and inventing bounds for it would put precision in the record that the source never offered.