timdorr/tesla-api

This system is a Ruby gem that serves as a client wrapper for the Tesla JSON API, enabling interaction with Tesla vehicles. It provides capabilities for vehicle state monitoring, command execution, and real-time telematics streaming via asynchronous WebSocket connections. The implementation utilizes modern authentication flows, including SSO with PKCE, and is supported by a comprehensive test suite using recorded API interactions.

The repository has been restructured with an initial commit that establishes the project's foundational files. This includes a new README detailing the Tesla JSON API and Ruby gem usage, a .gitbook.yml configuration for documentation hosting, and a .gitignore file tailored for Ruby development environments. Tooling configurations have been added, including .prettierrc for code formatting, .standard.yml for Ruby linting, .rspec for test runner settings, and .tool-versions specifying Ruby 3.2.2. The commit also introduces the MIT LICENSE, a Rakefile for running specs and an interactive console, and data files such as apiary.apib (noting a migration to a new documentation site) and ownerapi\_endpoints.json containing API endpoint definitions. Additionally, a vault.proto file defining protobuf structures for vault-related data has been added.

(repo-wide) · high confidence

The \lib/tesla\_api\ gem has been updated to version 3.1.0, introducing a new authentication flow that uses Tesla's Single Sign-On (SSO) with PKCE and enforces TLS 1.2 for login requests. The HTTP client has switched from HTTParty to Faraday, and the library now supports asynchronous WebSocket connections for real-time vehicle data streaming and autopark features via the \async\ gem. Existing vehicle control commands remain available, but the underlying connection and authentication mechanisms have changed to support these new capabilities.

_lib/tesla\api · high confidence

Added test coverage for Tesla API client authentication and vehicle control; Initial test infrastructure setup.

The tesla\_api gem is introduced as a wrapper for the Tesla JSON API, enabling users to check vehicle state, issue commands, and stream telematics data. The package declares runtime dependencies on async-websocket, faraday, and faraday\_middleware, while establishing a development environment with bundler 2, rspec, standard, vcr, webmock, dotenv, rotp, and rake.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• First survey — no prior run to compare against. CAI 60.

• Code Health 97
• Architecture 69
• Maturity 49
• Readiness 59
• Security 99

• 300 commits — 287 feature/other, 13 fixes

• docs/vehicle — 199 commits
• (root) — 26 commits
• docs/api-basics — 22 commits
• lib/tesla_api — 18 commits
• docs/energy — 9 commits
• .github/workflows — 8 commits
• docs/miscellaneous — 8 commits
• docs/README.md — 3 commits
• (repo) — 2 commits
• docs/SUMMARY.md — 2 commits
• .github/FUNDING.yml — 1 commit
• spec/cassettes — 1 commit
• spec/lib — 1 commit

• fix: BT42/37 add&fix (#391)
• fix: Document MFA, 3 Endpoints + Update ownerapi_endpoints.json + Typo fix + Add misc to vehicle state. (#666)
• fix: Fix cop
• fix: Fix issue w/ older Faradays (#386)
• fix: Fix link inside tripplan.md (#716)
• fix: Fix lint error
• fix: Fixed set_charging_amps + spec (#490)
• fix: Update endpoints + markdown error fix 🛠️ (#609)
• fix: Update info on what remote_boombox is + fix gitbook page ref (#670)
• fix: fix format
• fix: fix: BTX8 code
• fix: fix: Updated climate state json (#647)
• fix: fix: remove space
• change: 19” Kumho Majesty 9 Solus TA91
• change: Add & Update documentation for API endpoints 📚 (#577)
• change: Add APPB code
• change: Add Documentation & Update Endpoints file 📚🌐 (#578)
• change: Add MFA detection/support to login
• change: Add MT321 option code (#360)
• change: Add MT322
• …and 280 more

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

timdorr/tesla-api 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.