pip-audit
tan
Our great sponsors
pip-audit | tan | |
---|---|---|
22 | 1 | |
903 | 30 | |
2.2% | - | |
8.8 | 7.4 | |
6 days ago | 4 months ago | |
Python | Python | |
Apache License 2.0 | MIT License |
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.
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.
-
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
-
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.
tan
-
Black, the Uncompromising (Python) Code Formatter Is Stable
Congratulations. I'm a Python developer of 17+ years and Black is truly a huge blessing in the Python ecosystem.
That said, I'm a little sad to see it's gone stable without adding support for tabs, which would be extremely simple to add at this point (cf. https://github.com/jleclanche/tan/commit/e23c038167528bdacdd...). I have a lot of people using this tab-capable fork, that I did not advertise anywhere.
Łukasz seems to have a personal grudge against tabs which may be why the issue for tab support was closed early on, but there's a plethora of good reasons to support it behind a flag. I don't want to rehash those arguments here on HN but you think you could re-think the approach a bit?
I'd be happy to do a PR if it's not getting rejected right away with "no discussion allowed" like the last one was (before Black was moved to PSF maintainership).
What are some alternatives?
ochrona-cli - A command line tool for detecting vulnerabilities in Python dependencies and doing safe package installs
pre-commit-hooks.nix - Seamless integration of https://pre-commit.com git hooks with Nix.
npm-esbuild-audit
setup-dvc - DVC GitHub action
aura - Python source code auditing and static analysis on a large scale
tox-poetry-installer - A plugin for Tox that lets you install test environment dependencies from the Poetry lockfile
squelch
yapf - A formatter for Python files
in-toto - in-toto is a framework to protect supply chain integrity.
husky - Git hooks made easy 🐶 woof!
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.
dassana - Supercharge your alerts.