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.
Allows RubyMotion projects to easily embed the Converser SDK.
ios-converser-sdk
folder into vendor
directory (or alternatively just create a symbolic link). Create the vendor
directory if it does not exist. You should have something like this.$ ls vendor/ios-converser-sdk
/ConverserResources/ libVGConversationKit_universal.a include/
Rakefile
of your RubyMotion project and add the following require lines.require 'rubygems'
require 'motion-converser'
Rakefile
, set up the app_api_key
, server_url
and framework
variables in your application configuration block.Motion::Project::App.setup do |app|
# ...
app.converser.framework = 'vendor/ios-converser-sdk'
app.converser.app_api_key = 'APP API KEY'
app.converser.server_url = 'SERVER URL'
end
The ConverserEngine
singleton is available from any class in your application. You access this singleton by calling the ConverserEngine.instance
method.
See included sample-app for further information.
FAQs
Unknown package
We found that motion-converser 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.