Ruby wrapper for the API
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Ruby wrapper for the API.


gem install gems [pending]


Continuous Integration

Build Status

Usage Examples

require 'rubygems'
require 'gems'

# Returns some basic information about the rails gem
puts 'rails'

# Returns an array of active gems that match the query
puts 'cucumber'

# Returns an array of gem version details
puts Gems.versions 'coulda'

# Returns the number of downloads by day for a particular gem version
puts Gems.downloads 'coulda', '0.6.3'

# Returns an array of gem dependency details for all versions of given gems
puts Gems.dependencies ['rails', 'thor'] [pending]

# The following method requires password authentication
Gems.configure do |config| [pending]
  config.username ''
  config.password 'schwwwwing'

# Retrieve your API key using HTTP basic auth
Gems.api_key [pending]

# The following methods require authentication
Gems.configure do |config| [pending]
  config.key '701243f217cdf23b1370c7b66b65ca97'

# List all gems that you own
puts Gems.gems [pending]

# View all owners of a gem that you own
puts Gems.owners 'gemcutter' [pending]

# Add an owner to a RubyGem you own, giving that user permission to manage it
puts Gems.add_owner '', 'gemcutter' [pending]

# Remove a user's permission to manage a RubyGem you own
puts Gems.remove_owner '', 'gemcutter' [pending]

# List the webhooks registered under your account
puts Gems.web_hooks [pending]

# Add a webhook
puts Gems.add_web_hook 'rails', '' [pending]

# Remove a webhook
puts Gems.remove_web_hook 'rails', '' [pending]

# Test fire a webhook.
puts Gems.fire_web_hook 'rails', '' [pending]

# Submit a gem to
puts Gems.push 'gemcutter-0.2.1.gem' [pending]

# Remove a gem from's index
puts Gems.yank 'bills', '0.0.1', :platform => 'x86-darwin-10' [pending]

# Update a previously yanked gem back into's index
puts Gems.unyank 'bills', '0.0.1', :platform => 'x86-darwin-10' [pending]


In the spirit of free software, everyone is encouraged to help improve this project.

Here are some ways you can contribute:

  • by using alpha, beta, and prerelease versions
  • by reporting bugs
  • by suggesting new features
  • by writing or editing documentation
  • by writing specifications
  • by writing code (no patch is too small: fix typos, add comments, clean up inconsistent whitespace)
  • by refactoring code
  • by closing issues
  • by reviewing patches

Submitting an Issue

We use the GitHub issue tracker to track bugs and features. Before submitting a bug report or feature request, check to make sure it hasn't already been submitted. You can indicate support for an existing issuse by voting it up. When submitting a bug report, please include a Gist that includes a stack trace and any details that may be necessary to reproduce the bug, including your gem version, Ruby version, and operating system. Ideally, a bug report should include a pull request with failing specs.

Submitting a Pull Request

  1. Fork the project.
  2. Create a topic branch.
  3. Implement your feature or bug fix.
  4. Add documentation for your feature or bug fix.
  5. Run bundle exec rake doc:yard. If your changes are not 100% documented, go back to step 4.
  6. Add specs for your feature or bug fix.
  7. Run bundle exec rake spec. If your changes are not 100% covered, go back to step 6.
  8. Commit and push your changes.
  9. Submit a pull request. Please do not include changes to the gemspec, version, or history file. (If you want to create your own version for some reason, please do so in a separate commit.)


Copyright (c) 2011 Erik Michaels-Ober. See LICENSE for details.