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.
A Flake8 <http://flake8.readthedocs.org/en/latest/>
_ plugin that checks for the line continuation style to be in the preferred method according to PEP-8 <https://www.python.org/dev/peps/pep-0008/#maximum-line-length>
_, specifically:
The preferred way of wrapping long lines is by using Python's implied line continuation inside parentheses, brackets and braces. Long lines can be broken over multiple lines by wrapping expressions in parentheses. These should be used in preference to using a backslash for line continuation.
Via pip:
pip install flake8-continuation
The --user <https://pip.pypa.io/en/stable/user_guide/#user-installs>
__
flag is highly recommended for those new to pip <https://pip.pypa.io>
__.
This package adds a single new warning, C092: prefer implied line continuation inside parentheses, brackets, and braces as opposed to a backslash
. That error code was picked because ord('\\') == 92
.
FAQs
Flake8 Line Continuation Plugin
We found that flake8-continuation 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.