mrswitch/hello.js

A Javascript RESTFUL API library for connecting with OAuth2 services, such as Google+ API, Facebook Graph and Windows Live Connect

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 14th, 2026
Created on August 31st, 2011
Open Issues & Pull Requests: 194 (+0)
GitHub issues: Enabled
Number of forks: 607
Total Stargazers: 4,619 (+0)
Total Subscribers: 122 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 52.8 days
Mean response time: 686.0 days
90th percentile: 2326.9 days
Tracked items: 22

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 23
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,945 days
Stale 30+ days: 23
Stale 90+ days: 23

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • good first issue (9)
  • help wanted (8)
  • Endpoint (1)
  • released (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

hello.js is a client-side JavaScript SDK for authenticating with OAuth2 and OAuth1 web services and querying their REST APIs.

The library solves the problem of inconsistent authentication and API interfaces across different OAuth providers. Rather than writing separate integration code for each service, developers use hello.js to standardize authentication flows and API calls. The tool handles OAuth2 authentication directly and OAuth1 through a proxy, then normalizes responses from services like Google, Facebook, and Windows Live so that querying user profiles, contacts, albums, and photos follows the same patterns regardless of the underlying provider.

The tool suits developers building client-side web applications that need to integrate with multiple social or cloud services without managing separate authentication libraries for each. It is modular, allowing you to include only the providers your application needs. The README indicates a modern rewrite is available in the next version, suggesting consideration of that branch for new projects.

Development on the main branch appears to have stabilized, with the project maintaining its existing functionality while active development has shifted to a v2 rewrite available as a separate branch. The tool continues to support the core use cases documented in its demos and test suite.