# Changelog

> **This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.**

## Score

- CAI 63 → 67 (+4.3)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 75 → 99 (+24.7)
- Architecture 69 → 69 (+0.0)
- Maturity 54 → 59 (+4.7)
- Readiness 67 → 67 (+0.0)
- Security 97 → 100 (+2.9)

## Resolved (14)

- ChunkedIO.gets (cognitive 21) (lib/down/chunked_io.rb)
- ChunkedIO.gets (cyclomatic 16) (lib/down/chunked_io.rb)
- ChunkedIO.readpartial (cognitive 18) (lib/down/chunked_io.rb)
- High: security finding (details withheld)
- High: security finding (details withheld)
- Inconsistent accessor style for the charset property. Http and Wget use a method call (charset()), while Httpx uses a property access (charset).
- Inconsistent accessor style for the content_type property. Http, NetHttp, and Wget use a method call (content_type()), while Httpx uses a property access (content_type). This breaks consistency in how users retrieve the same information.
- Inconsistent method signatures for the 'open' operation across backend implementations. Similar to download(), NetHttp.open() takes only a URL, while Http/Httpx take (url, rewindable), and Wget takes (url, args, rewindable, options). This inconsistency makes it difficult to swap backends transparently.
- Inconsistent method signatures for the primary download operation across different backend implementations. While Down.download() and Down.Backend.download() provide a unified interface, the specific backend classes (Http, Httpx, NetHttp, Wget) expose vastly different signatures. NetHttp.download() only takes a URL, whereas Http/Httpx/Wget require numerous positional arguments for size limits, progress callbacks, and file handling. This forces users to know the specific backend's signature or rely on the top-level Down module, breaking polymorphism.
- Inconsistent property vs method access for metadata. Httpx exposes url, headers, charset, and content_type as properties, while Http and Wget expose url and headers as properties but content_type() and charset() as methods. This creates a confusing API where the same type of data is accessed differently depending on the backend.
- Medium: security finding (details withheld)
- Medium: security finding (details withheld)
- Medium: security finding (details withheld)
- Wget.download (cognitive 16) (lib/down/wget.rb)

## New (4)

- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)

## Changes since last survey

- 11 commits — 11 feature/other, 0 fixes

## By area

- (root) — 9 commits
- .github/workflows — 1 commit
- sig/generated — 1 commit

## Notable commits

- change: Add RBS type signatures
- change: Add security policy
- change: Bump actions/checkout to v7
- change: Bump to 5.6.2
- change: Delegate Down::ChunkedIO reading to a Tempfile or StringIO
- change: Don't report compressed Content-Length as ChunkedIO size (#104)
- change: Match IO behaviour in Down::ChunkedIO
- change: Pass response positionally to ResponseError on invalid redirects (#105)
- change: Reduce Down::ChunkedIO allocations, especially for IO.copy_stream
- change: Remove deprecated wget backend
- change: Remove top-level headers option in Down::NetHttp
