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.
migrate_factory_rails
Advanced tools
Completely rebuild your migrations to agilize setup and simplify schema
gem install migrate_factory_rails
or add to your Gemfile
group :development do
gem 'migrate_factory_rails'
end
Be careful, rebuild do not cover all situations yet then may miss some migration You can use two commands currently:
rake rebuild:migrations
-> Will rebuild all your migrations and save on tmp/rebuild
, then you can validate if it worths without lose any data.rake rebuild:cleanup
-> Will cleanup all data on tmp/rebuild
.My goal here was the challenge to rebuild every migrations from Rails, matching as close as possible the final schema.rb
meanwhile reducing strongly the amount of migrations. Specially on old projects, there will be a lot ot migrations, sometimes for a single column or index which extends the setup for a few seconds. If is worth or not to use, feel free to discuss.
FAQs
Unknown package
We found that migrate_factory_rails demonstrated a healthy version release cadence and project activity because the last version was released less than 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.