amro/gibbon
63.9
Adequate · 6 November 2026
470
lines of production code
Ruby
primary language
4
measurements over time
What this system is
Behavioural changes
Gibbon 4.0.0: Complete API rewrite with modern HTTP client and structured errors
This release replaces the previous HTTP implementation with a new architecture built on Faraday, introducing a fluent \Request\ builder that supports method chaining for all CRUD operations (create, retrieve, update, upsert, delete). The library now enforces TLS 1.2 as the minimum security standard and supports Faraday v2+ authentication patterns. Users gain access to a structured \Response\ object containing parsed bodies and headers, configurable symbol/string key handling, and detailed \MailChimpError\ exceptions that expose status codes, titles, and raw bodies for better debugging. The default read and open timeouts are set to 60 seconds, and proxy support is retained via environment variables or instance configuration.
lib/gibbon · high confidence
Gibbon 4.0.0: Ruby 3.1+ requirement and TLS 1.2+ minimum
Gibbon has been updated to version 4.0.0, which raises the minimum supported Ruby version to 3.1 (dropping support for EOL versions 2.4 through 3.0) and enforces TLS 1.2 or newer for connections. The release also modernizes the development setup by loosening RSpec pinning, removing Rubinius leftovers, and updating the CI matrix to cover Ruby 3.1 through 4.0.
(repo-wide) · high confidence
Test coverage
Initial RSpec test suite for Gibbon core components; Removal of placeholder test file.
Dependencies
Gibbon library initialization and dependency requirements
The lib/gibbon.rb file now explicitly requires Faraday, multi\_json, CGI, and Logger, and loads internal helper, error, request, and response modules. This establishes the runtime dependencies and module structure for the Gibbon wrapper, ensuring these components are available when the library is loaded.
lib · high confidence
Modernize gem dependencies and Ruby requirements
The gem now requires Ruby 3.1.0 or higher and relies on Faraday \>= 1.0 and multi\_json \>= 1.11.0 for core functionality. Development dependencies have been updated to RSpec \~\> 3.13, WebMock \~\> 3.8, and YARD \~\> 0.9, while legacy development tools like shoulda, bundler 1.x, jeweler, and rcov have been removed. The Gemfile now delegates to the gemspec, and the source URL has been switched to HTTPS.
(dependencies) · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 60 → 64 (+4.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 75 → 75 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 47 → 56 (+8.5)
- Readiness 67 → 67 (+0.0)
- Security 95 → 95 (+0.0)
Resolved (4)
- Ambiguous HTTP method mapping for create/update/upsert. In RESTful APIs, 'create' typically maps to POST, 'update' to PUT/PATCH, and 'upsert' to PUT/PATCH with conditional logic. However, without explicit documentation, it is unclear if 'update' and 'upsert' differ only in behavior (idempotency/conditional) or if they map to different HTTP verbs (PUT vs PATCH). This creates confusion for users regarding which method to use for partial vs full updates.
- Duplicate HTTP method exposure across two different classes. Both 'Gibbon.APIRequest' and 'Gibbon.Request' expose methods for performing HTTP operations (get, post, put, patch, delete). 'Gibbon.Request' also exposes 'create', 'update', 'upsert', and 'retrieve'. This duplication suggests unclear separation of concerns between the two classes, leading to confusion about which class should be used for making API calls.
- Off-boarding risk: anonymized user #1
- Redundant operations for fetching data. Both 'get' and 'retrieve' accept the same parameters and likely perform the same HTTP GET request. Having two methods for the same action violates the principle of least surprise and encourages inconsistent usage.
New (1)
- Off-boarding risk: anonymized user #1
Changes since last survey
- 9 commits — 8 feature/other, 1 fixes
By area
- (root) — 4 commits
- (repo) — 2 commits
- lib/gibbon — 2 commits
- spec/gibbon — 1 commit
Notable commits
- fix: Merge pull request #327 from dajiaohuang/fix/instance-false-boolean-config
- change: Bump version to 4.0.1
- change: Bump version to 4.1.0
- change: Constrain JSON to support the Ruby 3.1 MultiJson adapter
- change: Cover inherited settings and request-level false overrides
- change: Drop Ruby 3.1 from CI and add 4.1.0 changelog entry
- change: Honor explicit false request settings
- change: Merge pull request #329 from amro/drop-ruby-3.1
- change: Require Ruby 3.2 and multi_json 1.21.2, drop json constraint
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
amro/gibbon was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 6 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 7937baf259d83c7fd05bb95ccdbf3f2631823358 — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-60d1b390edf0.