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.
It's a pain to have to setup a testing environment when creating gems. This app includes a Rails skeleton that can be included in other gems so that everything is already setup.
Gem functionality can just be patched into existing classes, or you can make your own. For example, to test
Devise authentication in a gem, you could just make a new controller and inherit from Metova::Dummy::ApplicationController
.
class AuthenticationTestController < Metova::Dummy::ApplicationController
before_action :authenticate_user!
def secret
head :ok
end
end
describe AuthenticationTestController do
it 'returns a 401 when not authenticated' do
get :secret
expect(response.status).to eq 401
end
end
Add this line to your gem's gemspec:
spec.add_development_dependency 'metova-dummy'
TODO: Write usage instructions here
git checkout -b my-new-feature
)git commit -am 'Add some feature'
)git push origin my-new-feature
)FAQs
Unknown package
We found that metova-dummy 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.