[BUG] uv.lock not recognized as lockfile

[woutervh]

Bug Description

running agentready on a checkout of
https://github.com/libranet/autoread-dotenv

we have a uv.lock in the root, but it is not recognized

[jeremyeder]

Hi @woutervh thanks for filing! I have it setup where you have to be approved to do issue-to-PR. So let me see how it goes from here.

[jeremyeder]

@claude review this bug report. If its a bug, fix it on a feature branch and push a PR.

[github-actions]

Claude finished @jeremyeder's task —— View job • claude/issue-137-20251125-1555 • Create PR ➔

---

Investigation: uv.lock not recognized as lockfile

Todo List

• Review the screenshot to understand the issue
• Locate the lockfile assessor code
• Identify why uv.lock isn't being recognized
• Fix the assessor to recognize uv.lock
• Check for tests (none exist for stub assessors)
• Commit and push changes
• Provide PR creation link

Findings

The bug is confirmed and fixed. The LockFilesAssessor in src/agentready/assessors/stub_assessors.py:37-47 had a hardcoded list of recognized lockfiles, but uv.lock was missing.

Root Cause: uv.lock was not included in the lockfiles list, causing repositories using uv (Python's modern dependency manager) to incorrectly fail the lock files assessment.

Fix Applied: Added uv.lock to the recognized lockfiles list at line 43.

Changes Made

• src/agentready/assessors/stub_assessors.py: Added uv.lock to the recognized lockfiles list

The fix has been committed and pushed to the feature branch.

--- | Branch

[github-actions]

🎉 This issue has been resolved in version 2.8.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀