Description
The default branch contains a PostgreSQL-backed Flask crawler with queue, lease, retry, depth, and browser-worker logic, but the repository has no GitHub Actions workflows and no automated tests. It consequently also has no CodeQL analysis or dependency-vulnerability audit. CONTRIBUTING.md explicitly states that there is no automated suite, so changes can merge without exercising the documented queue and idempotency invariants or any automated security verification.
Expected Behavior
The repository has an automated test suite and CI that runs it across relevant Python versions and operating systems, with PostgreSQL-backed coverage for the queue, lease, retry, and depth behavior. CI also includes CodeQL and a scheduled dependency-vulnerability audit.
Reproduction Steps
- Inspect the default branch at commit
51a0474e8a4a86c8289dc73d9cc6c399469d9193.
- Query the repository's Actions workflows and observe a total count of
0.
- Read the
Tests section of CONTRIBUTING.md, which states that no automated suite exists.
- Inspect
stratz_scraper/database.py and stratz_scraper/web/ to confirm the shipped behavior is executable application code rather than static documentation.
Environment / Context
Default branch master, commit 51a0474e8a4a86c8289dc73d9cc6c399469d9193.
Discovered During
Task 2026-08-24-public-repository-audit — public Nitjsefnie and Nitjsefnie-Harness-Commons CI, bug, and security sweep.
Suggested Fix
Unverified: start with database-level tests for minimum-depth preservation, lease release, retry eligibility, and concurrent task claiming; run portable tests in an OS/Python matrix, PostgreSQL integration tests in a Linux service-container job, CodeQL, and a scheduled dependency audit.
Description
The default branch contains a PostgreSQL-backed Flask crawler with queue, lease, retry, depth, and browser-worker logic, but the repository has no GitHub Actions workflows and no automated tests. It consequently also has no CodeQL analysis or dependency-vulnerability audit.
CONTRIBUTING.mdexplicitly states that there is no automated suite, so changes can merge without exercising the documented queue and idempotency invariants or any automated security verification.Expected Behavior
The repository has an automated test suite and CI that runs it across relevant Python versions and operating systems, with PostgreSQL-backed coverage for the queue, lease, retry, and depth behavior. CI also includes CodeQL and a scheduled dependency-vulnerability audit.
Reproduction Steps
51a0474e8a4a86c8289dc73d9cc6c399469d9193.0.Testssection ofCONTRIBUTING.md, which states that no automated suite exists.stratz_scraper/database.pyandstratz_scraper/web/to confirm the shipped behavior is executable application code rather than static documentation.Environment / Context
Default branch
master, commit51a0474e8a4a86c8289dc73d9cc6c399469d9193.Discovered During
Task
2026-08-24-public-repository-audit— public Nitjsefnie and Nitjsefnie-Harness-Commons CI, bug, and security sweep.Suggested Fix
Unverified: start with database-level tests for minimum-depth preservation, lease release, retry eligibility, and concurrent task claiming; run portable tests in an OS/Python matrix, PostgreSQL integration tests in a Linux service-container job, CodeQL, and a scheduled dependency audit.