
Security News
Follow-up and Clarification on Recent Malicious Ruby Gems Campaign
A clarification on our recent research investigating 60 malicious Ruby gems.
Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file lib/title/processor
. To experiment with that code, run bin/console
for an interactive prompt.
TODO: Delete this and the text above, and describe your gem
Add this line to your application's Gemfile:
gem 'title-processor'
Or:
source "https://rubygems.pkg.github.com/nikitanaumenko" do
gem "title-processor", "0.1.3"
end
And then execute:
$ bundle install
Or install it yourself as:
$ gem install title-processor
Or from github registry:
$ gem install title-processor --version "0.1.3" --source "https://rubygems.pkg.github.com/nikitanaumenko"
From STDIN:
$ cat links.txt | title-processor
From File:
$ title-processor ./links.txt
FAQs
Unknown package
We found that title-processor 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
A clarification on our recent research investigating 60 malicious Ruby gems.
Security News
ESLint now supports parallel linting with a new --concurrency flag, delivering major speed gains and closing a 10-year-old feature request.
Research
/Security News
A malicious Go module posing as an SSH brute forcer exfiltrates stolen credentials to a Telegram bot controlled by a Russian-speaking threat actor.