Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
IrbBenchmark wraps irb
commands
evaluations in a Benchmark.measure{ ... }
block and displays the results after
the command execution. Example:
irb(main):001:0> sleep 1
0.000000 0.000000 0.000000 ( 1.000323)
=> 1
$ gem install irb-benchmark
$ irb -rirb-benchmark
.irbrc
require
require 'irb-benchmark'
Irbtools.add_library :irb_benchmark, late: true
Note that the former option can be used with irbtools too, so it is the preferred.
IrbBenchmark.enabled = true / false
irbtools integration
It auto-detects Wirb presence and FancyIrb configuration for colorized output (both are used by the well-known irbtools gem).
The usage with FancyIrb alters the benchmark measures adding a small overhead.
Fell free to open an issue for bugs or feature requests, or fork it and make a pull request.
janlelis and its
fancy_irb which saved me from spending
time to discover how to monkey-patch Irb
:-)
Copyright (c) 2012-2017 Maurizio De Santis. MIT license
FAQs
Unknown package
We found that irb-benchmark 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.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.