Weave Code
Oauth User Data Laravel Package
oryzone/oauth-user-data
Laravel package that fetches and normalizes user profile data from OAuth providers such as Google, Facebook, and GitHub. It offers a unified API to retrieve names, emails, avatars, and other fields after social login, with caching and configurable drivers for each provider.
Extension library for Lusitanian/PHPoAuthLib to extract user profile data from various oAuth providers
Frequently asked questions about Oauth User Data
- Is oryzone/oauth-user-data actually a Laravel package?
- Not in any meaningful sense. It is a thin extension layer on top of Lusitanian/PHPoAuthLib, a standalone OAuth 1.0a/2.0 client, that adds a getUserData()-style abstraction across providers. It ships no service provider, facade, config file, migration, or publishable assets. Using it in Laravel means authoring your own wrapper service provider, config binding, and provider registry, and owning that wrapper forever.
- How do I install oryzone/oauth-user-data with Composer?
- You would run composer require oryzone/oauth-user-data, but expect trouble immediately. The last release is February 2014 and was authored against the PHP 5.4 to 5.6 era, so Composer will almost certainly refuse to resolve the dependency tree against modern PHP 8 constraint sets. Getting it installed usually requires --ignore-platform-reqs hacks or a fork with a rewritten composer.json.
- Does oryzone/oauth-user-data support Laravel 10, 11, or 12?
- No. The package has no framework integration at all and has not seen a release since February 2014. Modern Laravel requires PHP 8.1 or 8.2 and up, while this library targets PHP 5.4 through 5.6, so neither Composer nor the runtime will cooperate without a hard fork. Treat it as incompatible on day one rather than something you can configure into working.
- Which OAuth providers does oryzone/oauth-user-data support?
- It provides user-data extraction over the PHPoAuthLib providers, historically including Facebook, Twitter, Google, LinkedIn, and similar networks. The implementations encode 2014-era API contracts: Facebook Graph v1 and v2 field shapes, Twitter's pre-X OAuth 1.0a endpoints, and a Google+ profile surface that no longer exists. Assume the extraction logic is stale against virtually every live provider today.
- How does oryzone/oauth-user-data compare to Laravel Socialite?
- Socialite is first-party, actively maintained, PHP 8 compatible, container-aware, and covers OAuth 2.0 user-profile retrieval for most providers. This package is an unmaintained 2014 add-on with roughly 44 stars and zero dependents. Adopting it means running two OAuth client stacks and duplicating credential and config management, with no clean composition story.
- What PHP version does oryzone/oauth-user-data require?
- It was written for the PHP 5.4 to 5.6 era and predates PHP 8 entirely. Running it on PHP 8.1 or 8.2 requires a fork with an updated composer.json and likely code-level fixes. Treat the PHP version gap as a hard compatibility blocker, not a minor constraint to negotiate around.
- Is oryzone/oauth-user-data maintained and safe for production authentication?
- Technical risk is very high. There is no maintainer signal, no release in over a decade, no CVE response path, and no community to absorb a fix for a security-sensitive OAuth surface. The two main failure modes are silent breakage when a provider rotates its user-info endpoint or response schema, and having no patch channel for the underlying OAuth client. The MIT license makes forking legally clean, but the fork becomes your liability, so decide ownership and maintenance budget first.
- How do I fetch a user's name, email, and avatar with oryzone/oauth-user-data?
- After the OAuth handshake, the package's getUserData()-style call returns normalized profile fields such as names, emails, and avatars across providers. That only works if the provider's current response schema still matches 2014 expectations, which is unlikely. In a modern Laravel app, Socialite's user() object plus a small mapping layer is the safer route, and this package's endpoint mappings are mainly useful as a reference during a port.
- Does oryzone/oauth-user-data support caching and configurable drivers?
- The description mentions caching and configurable drivers per provider, but the library ships no Laravel service provider, config file, or publishable assets. In practice any caching layer or driver configuration has to be wired up by you around the raw call. Budget that customization as part of any integration estimate.
- How do I migrate from oryzone/oauth-user-data to Laravel Socialite?
- Use a strangler-fig migration: stand up Socialite in parallel, route new logins through it, and retire PHPoAuthLib provider by provider as each is reimplemented as a Socialite driver or dropped for lack of use. Where a provider genuinely has no Socialite equivalent, write a small custom driver against Socialite's contract instead of resurrecting PHPoAuthLib. The only hard justification for adopting this package at all is a provider Socialite cannot cover, and even then a custom driver is usually a few days of work versus a full adoption cycle.
Weaver
How can I help you explore Laravel packages today?