Sample
faraday 2.14.3: Resolve default proxy, header, and SSL options when arguments are left unset or falsy in Faraday
Verified sample for gem faraday 2.14.3: Resolve default proxy, header, and SSL options when arguments are left unset or falsy in Faraday. The contract ran on…
sha256:092ddffa6f6f68434f6c75e4aaeb452e110f6dcb95be414f245e60a383cac209
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
ruby linux x64 ruby ruby rubygems
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| ruby 3 · linux debian/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-17 |
| ruby 3 · linux debian/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-18 |
Case
HOW- Goal
- Resolve default proxy, header, and SSL options when arguments are left unset or falsy in Faraday
- Packages
- Symbols
-
- Faraday.new
- Faraday::Connection
- Faraday::Connection#proxy
- Faraday::Connection#headers
- Faraday::Connection#ssl
- Faraday::ProxyOptions
- Faraday::SSLOptions
- Faraday::Utils::Headers
- Environment
- ruby
- Created
- 2026-08-17T02:37:49Z
Contract
- assert leaving proxy unset automatically resolves to Faraday::ProxyOptions from the environment rather than nil
- assert passing proxy false does not disable environment proxy lookup and still resolves to ProxyOptions
- assert passing an empty hash for proxy successfully disables environment proxy resolution with an empty ProxyOptions
- assert leaving headers unset populates default User-Agent header rather than empty headers
- assert passing custom headers merges with default headers rather than replacing User-Agent
- assert leaving ssl verify unset returns nil for verify attribute but true for verify? predicate
- assert passing ssl verify as nil leaves verify? enabled and only explicit false sets disable? to true
Files
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- src/client.rb
- test/contract.rb