# 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 50 → 55 (+5.4)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 65 → 65 (+0.0)
- Architecture 87 → 87 (-0.0)
- Maturity 37 → 53 (+16.3)
- Readiness 64 → 64 (+0.0)
- Security 54 → 49 (-5.5)

## Resolved (11)

- Documentation: no installation or build instructions (README.md)
- Documentation: no project overview (README.md)
- Documentation: no usage examples (README.md)
- Hotspot: lib/mongo/session.rb (lib/mongo/session.rb)
- Inconsistent naming for getter/setter pair. Ruby convention typically uses the same name for both (e.g., `credentials` for both getter and setter, or `get_credentials`/`set_credentials` if explicit). Using `credentials` for getter and `credentials=` for setter is standard, but the presence of `fetch` and `instance` methods nearby creates ambiguity about whether `credentials` is a simple accessor or a cached lookup.
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Orphaned file (lib/mongo/operation/map_reduce/result.rb)
- Orphaned file (lib/mongo/protocol/serializers.rb)
- Redundant methods with overlapping intent. `list_mongo_databases` appears to be a specific variant or alias of `list_databases`, but the parameter signature differs (`name_only` is explicit in the former, implicit or handled via `opts` in the latter). This creates confusion for users on which method to use for listing databases.
- While not a naming inconsistency per se, the presence of `==` and `hash` on `User` suggests value equality semantics, but `User` contains sensitive data (passwords, mechanisms). If `==` compares all fields including passwords, it may be a security risk or performance issue. If it compares only identity fields, the naming `==` is misleading compared to `eql?` or `identity_match?`.

## New (8)

- High secret: WD-SECRET-0005 (.evergreen/functions.sh)
- High: security finding (details withheld)
- Medium: security finding (details withheld)
- Medium: security finding (details withheld)
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #1
- Orphaned file (lib/mongo/srv/resolver.rb)
- Rotate the exposed credentials — git history can't be un-committed

## Changes since last survey

- 10 commits — 10 feature/other, 0 fixes

## By area

- lib/mongo — 5 commits
- (root) — 2 commits
- spec/spec_tests — 2 commits
- profile/driver_bench — 1 commit

## Notable commits

- change: Bump version to 2.26.1 (#3128)
- change: RUBY-3813 Support KMS connect callback for HTTP proxies (#3119)
- change: RUBY-3821 Remove pre-4.2 spec test fixtures (#3117)
- change: RUBY-3952 Add no more to spans that are not recording (#3124)
- change: RUBY-3952 Benchmark OpenTelemetry configurations with DriverBench (#3121)
- change: RUBY-3952 Cache tracing values that do not change (#3126)
- change: RUBY-3952 Cut allocations on the command tracing path (#3127)
- change: RUBY-3952 Skip span work for spans with invalid contexts (#3123)
- change: RUBY-3982 Enable Lint/UnreachableCode cop (#3114)
- change: RUBY-3986 Mandate raising writeConcernError (change SHOULD to MUST) (#3125)

## Architecture

- Unchanged — 0 containers · 1 contexts · 0 edges
