Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Strava Laravel Package

codetoad/strava

Laravel package for integrating the Strava API into your app. It simplifies OAuth authentication and access to athlete, activity, and stats data, making it easier to build fitness, training, and activity-tracking features with Strava.

View on GitHub
Deep Wiki
Context7

codetoad/strava is a Laravel package that wraps the Strava API in a clean, expressive client. It manages OAuth 2.0 authentication, token refresh, and API requests, letting you sync activities, athlete data, and more without boilerplate.

  • OAuth 2.0 flow with automatic token refresh
  • Fluent access to athletes, activities, segments, and clubs
  • Webhook support for real-time Strava events
  • Laravel facade and config-driven setup
  • Consistent error handling for API responses
Frequently asked questions about Strava
What is codetoad/strava used for in a Laravel application?
It is a Laravel package that wraps the Strava API, letting you authenticate users and retrieve activities, athlete stats, segments, and other Strava data through a fluent interface. It fits Laravel apps that need an integration adapter inside the service container, configuration, and facade patterns. Treat it as an API client, not a complete sync platform or domain model.
How do I install codetoad/strava in Laravel?
Install with Composer, rely on Laravel package discovery, publish the config, and add your Strava client credentials to environment configuration. The main effort is not installation but modeling OAuth scopes, token storage and refresh, rate limits, pagination, and webhooks. Pin the package version and test the upgrade in CI.
Which Laravel and PHP versions does codetoad/strava support?
The provided evaluation does not list explicit Laravel and PHP version constraints, so check the package's composer.json and README before committing. Compatibility with your target Laravel and PHP version should be the first step in your integration spike. Verify that it does not introduce conflicting HTTP clients or facade aliases.
Does codetoad/strava handle Strava OAuth authentication and token refresh?
The package is intended for authenticating Strava users and accessing Strava data, but the overview does not clearly separate API calls from full OAuth lifecycle handling. You must verify whether it supports authorization, token refresh, revocation, and encrypted token storage, or whether your application must own those concerns. Plan to store tokens securely and handle refresh in your application layer.
Does this package support Strava webhooks and event processing?
Webhook support is not confirmed in the provided overview, so treat subscription validation and event processing as something to verify. If you need near-real-time updates, the integration approach recommends adding Strava webhook subscription and event processing after read-only sync is stable. Queue-based processing and observability remain your responsibility.
How does codetoad/strava handle rate limits, pagination, and 429 responses?
The package is an API wrapper and is not documented here as providing automatic rate-limit handling, retries, backoff, or pagination. The integration plan says you should implement pagination, retry and backoff, rate-limit handling, and queue workers in your application. Test how the package surfaces 429 responses and design a fallback direct HTTP path.
Is codetoad/strava safe for production use?
The technical evaluation rates it moderate risk because of a small ecosystem footprint, zero dependents, and likely single-maintainer risk. A recent release is positive but does not prove production maturity. Isolate it behind an internal StravaClient or StravaGateway interface, add encrypted token storage, feature flags, audit logging, and a direct HTTP fallback before enabling it for all users.
How should I structure my code to use this package without vendor lock-in?
Wrap the package behind an internal interface such as StravaClient or StravaGateway so vendor-specific APIs do not leak into controllers and jobs. Keep a direct Strava HTTP fallback or adapter so you can migrate away without rewriting domain logic. This also makes testing and replacement easier if the package becomes stale.
Does codetoad/strava include tests, CI, and static analysis?
The provided overview does not confirm test coverage, CI, static analysis, or a documented upgrade path. Ask those questions directly and inspect the repository before adopting the package. Pin versions and test upgrades in CI as part of your compatibility checks.
What are alternatives to codetoad/strava if it becomes unmaintained?
Alternatives include direct Strava API v3 HTTP calls behind your own adapter or another maintained Strava client. Because the package has zero dependents and limited public production evidence, keep a fallback path planned. A fork or direct HTTP adapter should be available if the package becomes stale.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console