Which files explain how our weekly report selected its dependencies?
astral-sh/uv
uv records a Python project’s resolved dependencies and can recreate its environment. A reporting team can check whether a scheduled categorization job uses the reviewed code and packages before trusting a changed result.
Public GitHub facts reviewed Nov 22, 2026. Independent editorial profile; not a sponsored entry.
How is the score calculated?
Calculated on 22.11.2026. Missing public information receives no points. The index does not establish code quality, security, fitness, or future visibility.
What can uv help with?
Hand off the weekly report
Store a tiny anonymized input with three rows and their expected labels beside the project. Commit the project configuration and reviewed lockfile. Write down the interpreter and command used to produce the sample report.
Detect stale configuration in CI
Start from a clean checkout and run uv lock --check, followed by uv sync --locked. Run the project’s normal report command using uv run --locked. Compare the output with the fixture before scheduling the job.
Questions people ask before using uv
Which files explain how our weekly report selected its dependencies?
Read pyproject.toml for requested packages and version ranges. Read uv.lock for the resolved set and commit both files with the application. A copied virtual environment has machine-specific paths and is a poor handoff record.
How can CI flag a stale lock before it installs anything?
Run uv lock --check as its own step in the project directory. A nonzero result is actionable evidence that the checked-in project and lock need attention. Keep the later installation step so binary or system-level failures remain distinguishable.
When is --frozen a misleading choice for a release check?
--frozen uses the existing lock without checking whether it matches current project metadata. Use --locked when the release must fail on disagreement. Investigate the configuration change before approving a rewritten lock.
How should two analysts compare results across a time-zone boundary?
Keep a dated input file with explicit timestamps and an expected cutoff. Use the same checkout and interpreter on each machine. Compare included row IDs before totals so a shifted day boundary is visible even if the final counts match.
Why did a package installed yesterday disappear from the project environment?
An exact sync removes extraneous packages. If the reporting command imports it, record it in the correct project dependency group and update the lock in review. Avoid relying on one analyst’s hand-modified environment for scheduled work.
Can I review one parser upgrade without accepting a broad refresh?
Try uv lock --upgrade-package with that parser’s package name on a branch. Read all changes in uv.lock because dependent resolutions may move. Run a fixture that covers empty values, redirects and one previously misparsed row.
How do I distinguish an unavailable Python wheel from a bad reporting rule?
Run sync on the target platform and save the installation failure separately from application logs. If sync succeeds, execute the report against the saved input. Reproducing the failure at the same stage narrows the diagnosis.
What still changes when a teammate checks out the same lockfile?
Environment variables, system libraries, accessible package indexes and live input data can differ. Record the Python and uv versions and capture the report’s input digest during a handoff. Compare one known row before reconciling totals.
When is advertools the component I need to investigate?
If the environment installs and a specific sitemap or crawl operation behaves unexpectedly, reduce it to a small library example. Compare the result with advertools documentation. Updating a package manager alone will not change the underlying analysis rule.
Can my team package every locked dependency under uv’s own license?
Check the individual licenses for the libraries and any tools bundled in your distribution. uv’s own MIT or Apache-2.0 choice applies to the covered project source. Archive applicable notices alongside the actual release contents.
What to check before adoption
- Primary language
- Rust
- GitHub license field
- Apache-2.0
- License according to repository file
- Apache-2.0 OR MIT · LICENSE ↗
- Stars / forks in this snapshot
- 92,550 / 3,926
- Last code push
- 22.11.2026
- Self-hostable
- Potentially, verify operating requirements
A package lock does not freeze the contents of an API, time-zone rules in external services or browser binaries installed elsewhere. Keep inputs and those runtime details with the report when comparisons matter.
Comparison and original sources
Compared with advertools advertools provides marketing data operations. uv helps reproduce the package environment in which an analyst runs them.
Documentation and repository data
Compare related projects
lighthouse
GoogleChrome/lighthouse
An automated audit tool for web performance, accessibility, SEO checks, and best practices.
GitHub snapshot 11.11.2026 · Score method on profile
A visual low-code environment for event-driven automations and integrations.
GitHub snapshot 11.11.2026 · Score method on profile
wordpress-develop
WordPress/wordpress-develop
A GitHub mirror of the WordPress core development project.
GitHub snapshot 11.11.2026 · Score method on profile
Back to Open Source Radar
Explore more projects by job, technology, and license.