Linkedin Laravel Package

Product Decisions This Supports

• Feature: "Sign in with LinkedIn" for auth flows. Decides whether to add LinkedIn as a first-class identity provider alongside email/password and other social logins in a Laravel app.
• Roadmap sequencing for social login expansion. Informs whether LinkedIn ships now, later, or never — useful when prioritizing B2B/professional-audience providers (LinkedIn) versus consumer ones (Google, Apple, Facebook).
• Build vs buy for OAuth. Shifts the decision from "write and maintain our own LinkedIn OAuth client" (token exchange, OIDC discovery, scope handling, token refresh, edge cases) to "adopt a maintained provider and spend engineering on product, not plumbing."
• Acquisition/activation experiments. Enables A/B tests of LinkedIn sign-up on landing pages, gated content, or trial flows for professional/B2B segments where LinkedIn identity is the low-friction option.
• Profile enrichment use cases. LinkedIn's userinfo returns name, email, picture, and (subject to scope/consent) headline/positions — supports onboarding pre-fill and "import your professional profile" style features.
• Dependency and risk posture. With a last release of 2024-11-27 and a 12-star "read-only subtree split" repo, the package's apparent low signal is an artifact of the split — the real project lives at SocialiteProviders/Providers. This is a decision input for your OSS dependency policy, not a quality signal by itself.
• Ecosystem fit confirmation. Reinforces Laravel-native architecture decisions: Socialite + this provider is the idiomatic path, keeping auth consistent with the rest of the stack.

When to Consider This Package

Consider adopting when:

• You are on Laravel/PHP and already (or plan to) use Laravel Socialite. This package is a drop-in provider — the integration cost is a config entry plus a callback route.
• Your target user is professional/B2B. LinkedIn login reduces friction and signals audience fit; it is often the expected option on B2B SaaS sign-up pages.
• You want OIDC-standard behavior and minimal custom OAuth code — the provider handles the LinkedIn-specific endpoints and scope quirks for you.
• You want a single-responsibility dependency (auth only) rather than a broad, opinionated SDK.
• You are comfortable consuming from the SocialiteProviders family — a widely used, community-maintained set of providers — and can pin a version and monitor upstream.

Look elsewhere when:

• You are not on Laravel/Socialite — the value is the Socialite contract; outside it you are paying for indirection.
• You need LinkedIn platform APIs beyond auth/profile — Share, Marketing/Ads, Pages, Talent, or Messaging. This package is authentication-only; those require the official LinkedIn API or partner access.
• You require a commercial SLA, vendor support, or security review artifacts — this is community OSS with no support contract.
• Your compliance posture prohibits subtree-split or thinly-starred mirrors as dependency sources; you may prefer to depend on the umbrella socialiteproviders/providers package or vendor/pin the source directly.
• You need enterprise SSO/SAML or workforce identity — that is a different product (e.g., OIDC/SAML with an IdP), not social login.
• You are heavily customizing the flow (custom scopes, multi-tenant token storage, unusual consent UX) to the point where the abstraction gets in the way.

Caveats to weigh, not reject on:

• The 12 stars are not comparable to a standalone package — this repo is a generated split. Evaluate the upstream project's activity and issue history instead.
• LinkedIn's API and policy surface changes; you inherit upstream's ability to track those changes. Check upstream commit cadence against your risk tolerance for auth-path dependencies.

How to Pitch It (Stakeholders)

For executives (one paragraph): "We can add 'Sign in with LinkedIn' to our Laravel app at very low cost and low risk. Rather than building and maintaining a LinkedIn login integration ourselves — which means ongoing work every time LinkedIn changes its API — we adopt a small, focused, community-maintained package that is the standard way to do this in our stack. It gives our B2B users a one-click, familiar sign-up path, which should reduce friction at the top of the funnel and improve conversion for professional audiences. The dependency is narrow (it only handles login and basic profile — no data sprawl), easy to remove, and requires minimal engineering to ship. The one thing to flag is that it is community open source without a commercial SLA, so we should pin the version and treat it as a monitored dependency — normal practice for our auth stack."

For engineering:

• Idiomatic Laravel/Socialite provider; integration is config + callback route, no custom OAuth code.
• Keeps LinkedIn-specific endpoint/scope handling out of our codebase; upstream absorbs API changes.
• Scope is intentionally narrow (auth + profile). Do not expect Share/Marketing/Pages APIs here — those are a separate decision.
• This repo is a read-only subtree split of SocialiteProviders/Providers; low star count is not a signal. Review the upstream project's activity, pin a version, and add it to the dependency-watch list.
• Last release 2024-11-27 — no red flag today, but define an owner and a trigger (e.g., upstream inactivity or a LinkedIn auth change) for reassessing.