Mirror of metasploit
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.


Hello, World!

Thanks for your interest in making Metasploit -- and therefore, the world -- a better place! Before you get started, review our Code of Conduct. There are mutliple ways to help beyond just writing code:

Contributing to Metasploit

Here’s a short list of do’s and don’ts to make sure your valuable contributions actually make it into Metasploit’s master branch. If you do not care to follow these rules, your contribution will be closed. Sorry!

Code Contributions

  • Do stick to the Ruby style guide and use Rubocop to find common style issues.
  • Do follow the 50/72 rule for Git commit messages.
  • Do license your code as BSD 3-clause, BSD 2-clause, or MIT.
  • Do create a topic branch to work on instead of working directly on master to preserve the history of your pull request. See PR#8000 for an example of losing commit history as soon as you update your own master branch.

Pull Requests

  • Do target your pull request to the master branch.
  • Do specify a descriptive title to make searching for your pull request easier.
  • Do include console output, especially for witnessable effects in msfconsole.
  • Do list verification steps so your code is testable.
  • Do reference associated issues in your pull request description.
  • Don’t leave your pull request description blank.
  • Don’t abandon your pull request. Being responsive helps us land your code faster.

Pull request PR#9966 is a good example to follow.

New Modules

  • Do set up msftidy to fix any errors or warnings that come up as a pre-commit hook.
  • Do use the many module mixin APIs.
  • Don’t include more than one module per pull request.
  • Do include instructions on how to setup the vulnerable environment or software.
  • Do include Module Documentation showing sample run-throughs.
  • Don’t submit new scripts. Scripts are shipped as examples for automating local tasks, and anything “serious” can be done with post modules and local exploits.

Library Code

  • Do write RSpec tests - even the smallest change in a library can break existing code.
  • Do follow Better Specs - it’s like the style guide for specs.
  • Do write YARD documentation - this makes it easier for people to use your code.
  • Don’t fix a lot of things in one pull request. Small fixes are easier to validate.

Bug Fixes

  • Do include reproduction steps in the form of verification steps.
  • Do link to any corresponding Issues in the format of See #1234 in your commit description.

Bug Reports

Please report vulnerabilities in Rapid7 software directly to security@rapid7.com. For more on our disclosure policy and Rapid7’s approach to coordinated disclosure, head over here.

When reporting Metasploit issues:

  • Do write a detailed description of your bug and use a descriptive title.
  • Do include reproduction steps, stack traces, and anything that might help us fix your bug.
  • Don’t file duplicate reports; search for your bug before filing a new report.

If you need some more guidance, talk to the main body of open source contributors over on our Metasploit Slack or #metasploit on Freenode IRC.

Finally, thank you for taking the few moments to read this far! You’re already way ahead of the curve, so keep it up!