ScribeJava configures a provider in one ServiceBuilder line
Simple OAuth library for Java
At a glance
- What is it?
- A Java OAuth client whose configuration is a builder call, whose HTTP transport is a maven module you pick, and whose newest release tag is older than its last push. What the README covers.
- Who is it for?
- ScribeJava fits a Java service that needs OAuth 1.0a or OAuth 2.0 across many providers and does not want to hand write each handshake: the builder line, the per client maven module and the per provider example classes cover the common flows. If your team needs state validation, token storage or a retry policy, confirm how ScribeJava handles them before adopting it.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Activity is slowing. The repository last received commits 6 months ago.
- What is it written in?
- Mainly Java, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- scribejava/scribejava5,451 ★ · -3
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| scribejava/scribejava | 5.5k | 5.5k |
-3 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
One ServiceBuilder line builds the whole service object
The unit of configuration is a builder call, not an annotation and not a properties file. A client is created by handing the identifier and the secret to a ServiceBuilder and naming the provider to build against.
OAuthService service = new ServiceBuilder(YOUR_CLIENT_ID)
.apiSecret(YOUR_CLIENT_SECRET)
.build(LinkedInApi20.instance());Everything else in the library hangs off that object, and the README makes the point by saying that this single line, with newlines added for readability, is all you need to configure ScribeJava with LinkedIn. The provider argument is a singleton such as LinkedInApi20.instance(), which is why each supported API is a class rather than a row in a config file. Nothing in the line says which grant type, scope or callback URL to use; those arrive later, when the service object is asked to build a request or to read a response.
The maven module you add is what picks your HTTP client
ScribeJava does not ship one HTTP stack. Each transport sits in its own maven module and you add the one you want to your pom.
scribejava-httpclient-ning
scribejava-httpclient-ahc
scribejava-httpclient-okhttp
scribejava-httpclient-apache
scribejava-httpclient-armerianing async http client 1.9.x covers the first module, asynchttpclient 2.x the second, then OkHttp, Apache HttpComponents HttpClient, and Armeria, which needs Java 8 or newer. A sixth route is any externally created HTTP client, demonstrated in an example named for Vkontakte. Every choice comes with a matching example class: FacebookAsyncNingExample, Google20AsyncAHCExample, GitHubAsyncOkHttpExample, FacebookAsyncApacheExample and Google20ArmeriaExample. The cost of the choice is that the module list and the provider list are separate, and a project that wants a specific transport still has to resolve the provider set on top of it.
Java 7 at runtime, Java 9 to compile from source
Compatibility is stated in two halves, and the halves pull in different directions for a build pipeline. The library is Java 7 compatible and is said to work in old environments and in Android apps, which is what lets it sit inside a legacy service that cannot be upgraded. The same section adds the catch: compiling from sources needs Java 9 or newer. A team on a Java 7 runtime can therefore depend on a published artifact and still be unable to build the project itself with the toolchain it runs on. The Armeria client raises the floor once more, since it requires Java 8, which removes one of the six transports on the oldest target.
Nine flows, each pointed at a runnable example class
Flow coverage is enumerated by RFC, which is the fastest way to see the shape of it: the authorization code grant, the resource owner password credentials grant and the client credentials grant from RFC 6749, refreshing an access token from section 6 of the same document, bearer token usage from RFC 6750, PKCE from RFC 7636, token revocation from RFC 7009, the device authorization grant from RFC 8628, and the OAuth 1.0 protocol in full from RFC 5849. Most lines link to an example class under the examples folder: Google20Example for the authorization code flow, VkontakteClientCredentialsGrantExample for client credentials, Google20WithPKCEExample, Google20RevokeExample, Google20DeviceAuthorizationGrantExample, and TwitterExample for OAuth 1.0. The resource owner password credentials grant and RFC 6750 bearer token usage are the entries with no example attached.
Providers are classes in scribejava-apis, not config entries
The provider catalogue is source code rather than configuration. The repository splits into scribejava-core for the library itself and scribejava-apis for the provider definitions, with one module per HTTP client and a scribejava-java8 module alongside them. The count given is 50 or more major 1.0a and 2.0 APIs, and the visible names run alphabetically: Asana, Automatic, AWeber, Box, Dataporten, Digg, Discord, Доктор на работе, Dropbox, Etsy and Facebook. Each provider is reached through a singleton passed into build(), which is why adding a service means adding a class rather than editing a table of endpoints. The example files live in the same module under src/test/java/com/github/scribejava/apis/examples, so the reference code and the provider definitions sit in one place.
The newest tag is from 2023, the last push is from 2026
Version history and repository activity tell different stories here. The most recent release is scribejava-8.3.3, published on 2023-01-25, preceded by 8.3.2 on 2022-10-10 and 8.3.1 on 2021-05-11. The last push to the default branch master was on 2026-05-18, and the repository is not archived. That gap between the newest tag and the last push is the thing to weigh before pinning a version, because the published artifact and the head of master are not the same code. History is kept in the tree as a changelog file next to v1-changelog and v2pre-changelog, and static analysis configuration sits in checkstyle.xml and pmd.xml at the root next to the parent pom.xml.
State validation, token storage and retries are left to you
Several things an OAuth client is normally expected to handle are not covered in the README's opening sections, so check the rest of the README and the examples before relying on them. Refreshing an access token is supported under RFC 6749 section 6, which is the protocol step rather than a storage decision. Thread safety gets a single line, an invitation to hit the library as hard and with many threads as you like, with no measurement attached.
Editorial conclusion
ScribeJava fits a Java service that needs OAuth 1.0a or OAuth 2.0 across many providers and does not want to hand write each handshake: the builder line, the per client maven module and the per provider example classes cover the common flows. If your team needs state validation, token storage or a retry policy, confirm how ScribeJava handles them before adopting it. Before pinning a version, compare the 8.3.3 tag from 2023-01-25 with the master branch, pushed on 2026-05-18, and decide which one you are depending on.
Frequently asked questions
How can I use OAuth with Java?
ScribeJava is a Java OAuth client library for it. You create a service with new ServiceBuilder(YOUR_CLIENT_ID).apiSecret(YOUR_CLIENT_SECRET).build(LinkedInApi20.instance()), add the maven module for the HTTP client you want, and then pick a flow: authorization code, client credentials, refresh, PKCE, device authorization grant, token revocation, or OAuth 1.0 for providers such as Twitter.
Which maven module do I add to my pom for OkHttp?
scribejava-httpclient-okhttp. The other modules are scribejava-httpclient-ning, scribejava-httpclient-ahc, scribejava-httpclient-apache and scribejava-httpclient-armeria, and the library also accepts any externally created HTTP client. The Armeria module requires Java 8 or newer.
Can ScribeJava run on Java 7?
The library itself is Java 7 compatible and is said to work in old environments and in Android apps, but compiling from sources needs Java 9 or newer. The Armeria HTTP client needs Java 8, so it drops out of the list on a Java 7 target.
What is the latest ScribeJava version?
The most recent release is scribejava-8.3.3, published on 2023-01-25, after 8.3.2 on 2022-10-10 and 8.3.1 on 2021-05-11. The default branch master was last pushed on 2026-05-18, which is later than that tag, so the branch and the published artifact are not the same point in history.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/scribejava-scribejava)Star history chart for your README
[](https://hysenlabs.com/projects/scribejava-scribejava)Was this useful?