aura
pip-audit
Our great sponsors
aura | pip-audit | |
---|---|---|
3 | 22 | |
485 | 917 | |
0.8% | 2.8% | |
4.3 | 8.8 | |
7 months ago | 1 day ago | |
Python | Python | |
GNU General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
aura
- Aura – Python source code auditing and static analysis on a large scale
-
A Large-Scale Security-Oriented Static Analysis of Python Packages in PyPI
I've done extensive research in this area and looked at existing tools including bandit to scan the whole pypi repository and monitor what is being uploaded there, the conclusion was that most of the tools are not up for this task so I made a new framework from scratch that is specially design for this purpose, to scan the whole PyPI repository, it's called Aura: https://github.com/SourceCode-AI/aura
-
Ever npm/pip installed malware? A modest call for action
Consider contributing your talents to projects that seek to improve the security of these registries. One project worth your attention is Aura, a Python source code auditing and static analysis tool. For those who want to explore Python malware detection challenges identified as important by the Python Software Foundation, see here. Consider contributing malware checks to the Python Package Index codebase, aka Warehouse.
pip-audit
-
Smooth Packaging: Flowing from Source to PyPi with GitLab Pipelines
Next up is making sure, none of the dependencies used throughout the project brings with it any already identified security issue. The makefile target audit, invokes the handy tool pip-audit.
-
Show HN: One makefile to rule them all
Here is my "one true" Makefile for Python projects[1]. The skeleton gets tweaked slightly each time, but it's served me well for 4+ years.
[1]: https://github.com/pypa/pip-audit/blob/main/Makefile
-
Pyscan: A command-line tool to detect security issues in your python dependencies.
Why use this over the established https://pypi.org/project/pip-audit/ ?
-
How Attackers Can Sneakily Slip Malware Packages Into Poetry.lock Files
https://pypi.org/project/pip-audit/ details usage and the GitHub Action install.
- How to improve Python packaging, or why 14 tools are at least 12 too many
-
Underappreciated Challenges with Python Packaging
If it's pure Python, the only packaging file you need is `pyproject.toml`. You can fill that file with packaging metadata per PEP 518 and PEP 621, including using modern build tooling like flit[1] for the build backend and build[2] for the frontend.
With that, you entire package build (for all distribution types) should be reducible to `python -m build`. Here's an example of a full project doing everything with just `pyproject.toml`[3] (FD: my project).
[1]: https://github.com/pypa/flit
[2]: https://github.com/pypa/build
[3]: https://github.com/pypa/pip-audit
-
Auditing your python environment
- repo: https://github.com/trailofbits/pip-audit rev: v2.4.3 hooks: - id: pip-audit args: [ "-r", "requirements.txt" ] ci: # Leave pip-audit to only run locally and not in CI # pre-commit.ci does not allow network calls skip: [ pip-audit ]
-
How to create a Python package in 2022
This is really nicely written; kudos to the author for compiling a great deal of information in a readable format.
If I can be forgiven one nitpick: Poetry does not use a PEP 518-style[1] build configuration by default, which means that its use of `pyproject.toml` is slightly out of pace with the rest of the Python packaging ecosystem. That isn't to say that it isn't excellent, because it is! But you the standards have come a long way, and you can now use `pyproject.toml` with any build backend as long as you use the standard metadata.
By way of example, here's a project that's completely PEP 517 and PEP 518 compatible without needing a setup.py or setup.cfg[2]. Everything goes through pyproject.toml.
[1]: https://peps.python.org/pep-0518/
[2]: https://github.com/trailofbits/pip-audit/blob/main/pyproject...
-
I think the CTX package on PyPI has been hacked!
Checking could be done if something like this eventually shows up in safety or pip-audit.
-
Open-source way to scan dependencies for CVEs?
Something like python's pip-audit. For commercial solutions I know there's Snyk and Jfrog we can always purchase, but I'm interested to see if there's an open-source tool that can do this.
What are some alternatives?
pytype - A static type analyzer for Python code
ochrona-cli - A command line tool for detecting vulnerabilities in Python dependencies and doing safe package installs
pyt - A Static Analysis Tool for Detecting Security Vulnerabilities in Python Web Applications
git-hooks.nix - Seamless integration of https://pre-commit.com git hooks with Nix.
anchore-engine - A service that analyzes docker images and scans for vulnerabilities
npm-esbuild-audit
Mobile-Security-Framework-MobSF - Mobile Security Framework (MobSF) is an automated, all-in-one mobile application (Android/iOS/Windows) pen-testing, malware analysis and security assessment framework capable of performing static and dynamic analysis.
setup-dvc - DVC GitHub action
Flake8 - flake8 is a python tool that glues together pycodestyle, pyflakes, mccabe, and third-party plugins to check the style and quality of some python code.
tox-poetry-installer - A plugin for Tox that lets you install test environment dependencies from the Poetry lockfile
squelch
tan - The uncompromising Python code formatter