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.
behave-html-formatter
Advanced tools
To use it with behave create behave.ini
file in project folder (or in home) with
following content:
# -- FILE: behave.ini
# Define ALIAS for HtmlFormatter.
[behave.formatters]
html = behave_html_formatter:HTMLFormatter
and then use it by running behave with -f
/--format
parameter, e.g.
behave -f help
behave -f html
behave -f html -o behave-report.html
You can find information about behave and user-defined formatters in the behave docs.
You want to help with improving this software? Please create an issue in our open bug tracker, or open a pull request directly.
We use tox for running linting and tests, e.g.
tox
tox -l
tox -e flake8,behave
For code formatting we use black, which you can run using our Tox setup, e.g.
tox -e black
If you need to change CSS or JavaScript code: First edit the regular files, then generate the minified versions like so:
tox -e minify
FAQs
HTML formatter for Behave
We found that behave-html-formatter demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 5 open source maintainers 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.