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 is the Ruby client library for interacting with the Foxtrot API. The only endpoint currently exposed is the route optimization endpoint (Foxtrot::Client.optimize!
).
In order to make requests, you need a valid API key. Your API key can be found at the bottom of any page in the Foxtrot web app.
gem install foxtrot-client
data = {
file_url: "https://www.domain.io/your_file.xlsx",
file_name: "your_file.xlsx",
geocode: "false",
stop_name: "Customer",
lat: "Lat",
lng: "Long",
load: "Load",
service_time: "Service Time",
time_window: "Time Window",
extra_info: "Contact Info",
date_starting: "1407712069593",
warehouse: "77 Massachusetts Ave, Cambridge MA",
num_drivers: 1,
num_avg_service_time: 10,
float_fuel_cost: 3.56,
float_driver_wage: 6.01,
float_mpg: 8.32
}
api_key = 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'
require 'foxtrot'
fox = Foxtrot::Client.new api_key
resp = fox.optimize!(data).poll_and_block!
result = resp.get_result
FAQs
Unknown package
We found that foxtrot-client 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.