
Product
Reachability for Ruby Now in Beta
Reachability analysis for Ruby is now in beta, helping teams identify which vulnerabilities are truly exploitable in their applications.
Times how long each Rake task takes. If your Rake build starts to get too long, it can be useful to quickly see how long each task is taking. It can also be useful to track Tasks over time.
In your Rakefile, add:
require 'rake-timer'
time_tasks
By default, time stats are written to the console. Optionally, you can write (append) to a CSV file (in reports/rake-timer.csv), which can easily be read by a charting library such as Highcharts.
Even more optionally, you can output results to the very nice statsd. Each task gets its own time-based set of graphs, so you can see how your build time is affected over, well time.
A full set of configuration options would be:
time_tasks :to => [:csv, :statsd], :unit => :milliseconds, :host => 'localhost', :port => 8125
Host and port are the statsd daemon you prepared earlier.
RakeTimer is packaged as a Gem. Install with:
gem install rake-timer
Copyright (c) 2011 Peter Moran. See LICENSE for details.
FAQs
Unknown package
We found that rake-timer demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Product
Reachability analysis for Ruby is now in beta, helping teams identify which vulnerabilities are truly exploitable in their applications.

Research
/Security News
Malicious npm packages use Adspect cloaking and fake CAPTCHAs to fingerprint visitors and redirect victims to crypto-themed scam sites.

Security News
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.