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.
Quick links: Taurus Documentation | Knowledge Base | Support Forum
Hides the complexity of performance and functional tests with an automation-friendly convenience wrapper. Taurus relies on JMeter, Gatling, Locust.io, and Selenium WebDriver as its underlying tools. Free and open source under Apache 2.0 License.
Just install it using PyPi:
pip install bzt
More detailed instructions for Linux, Mac OS and Windows available here.
Create a file named test.yml
with following contents:
---
execution:
- concurrency: 10
ramp-up: 1m
hold-for: 1m30s
scenario: simple
scenarios:
simple:
think-time: 0.75
requests:
- http://blazedemo.com/
- http://blazedemo.com/vacation.html
Then run bzt test.yml
. After the tool finishes, observe resulting summary stats in console log (more reporting options here). All artifact files from the run will be placed in the directory mentioned in console log. Read more on command-line tool usage here.
FAQs
Taurus Tool for Continuous Testing
We found that bzt 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.