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.
spree_product_activator
Advanced tools
Simple way to make active/inactive a product
You're going to be able to see a checkbox to make a product active/inactive as you need, this in product admin site
Now you can use it like here:
Spree::Product.without_inactive
or
Spree::Product.with_inactive
Add spree_product_activator to your Gemfile:
gem 'spree_product_activator'
Bundle your dependencies and run the installation generator:
bundle
bundle exec rails g spree_product_activator:install
Be sure to bundle your dependencies and then create a dummy test app for the specs to run against.
bundle
bundle exec rake test_app
bundle exec rspec spec
When testing your applications integration with this extension you may use it's factories. Simply add this require statement to your spec_helper:
require 'spree_product_activator/factories'
Copyright (c) 2014 jtapia, released under the New BSD License
FAQs
Unknown package
We found that spree_product_activator 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.