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.
This gem uses FFI to provide Ruby method bindings for the pigpio C library. This makes the Raspberry Pi GPIO pins usable in Ruby.
NOTE: This is for Ruby on Linux, not for the Raspberry Pi Pico (W).
Install pigpio with:
sudo apt-get install pigpio
Install this gem as root:
sudo gem install pigpio_ffi
Ruby scripts need to be run as root:
sudo ruby my_script.rb
require 'pigpio_ffi'
PiGPIO.gpioInitialise
PiGPIO.gpioSetMode(4, 1)
10.times do
PiGPIO.gpioWrite(4, 1)
sleep 0.5
PiGPIO.gpioWrite(4, 0)
sleep 0.5
end
# This must be called or the script will block forever.
PiGPIO.gpioTerminate
This will blink an LED attached to GPIO 4, every half second, for 10 seconds total.
As much as possible, the class methods of PiGPIO
follow the function names and argument formats of the pigpio C functions. These can be found in its documentation, located here.
Exceptions:
TODO: List methods with different interfaces, and unmapped methods here.
FAQs
Unknown package
We found that pigpio_ffi 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.