Skip to content

~95% on SimpleQA (e.g. Qwen3.6-27B on a 3090). Supports all local and cloud LLMs (llama.cpp, Ollama, Google, ...). 10+ search engines - arXiv, PubMed, your private documents. Everything Local & Encrypted.

28.1 KB
Raw Blame

Workflow Status

Live status of every GitHub Actions workflow in this repo. Auto-generated by scripts/generate_workflow_status.py. Do not edit between the generated markers — regenerate with pdm run python scripts/generate_workflow_status.py. Anything outside the markers is preserved on regeneration.

How to read this page

  • Live badges (right column on active gates) re-render on every page view and reflect the current head-of-default-branch status from GitHub. Click one to land on that workflow's runs page. The badge is the source of truth for current status — there is intentionally no static status column, because that would flip every regeneration as the most-recent run cycles through success → skipped → in_progress.
  • Last activity uses coarse calendar buckets — last 30 days, 1-3 months ago, 3-6 months ago, long ago, never. Exact dates would change every regeneration; buckets only change when a workflow drifts, which is the signal worth seeing in version-bump diffs.
  • Disabled = a caller has the uses: line commented out, or the workflow is disabled in the GitHub UI. Stale = scheduled trigger but no successful run within 2× its cron cadence (and ≥60 days). The three top sections are the action items.
  • Reusable workflows (whose only non-gate triggers are workflow_dispatch or pull-request events) show their gated run — the most recent run of their parent (release.yml, release-gate.yml, ci-gate.yml) that included them — not their own empty direct-run history.

78 workflows: 1 disabled · 2 stale · 1 manual-only · 74 active

⚠ Disabled workflows

Workflow Disabled where Last direct run
nuclei.yml release-gate.yml:219 (commented) never

⚠ Stale (scheduled but no recent successful run)

Workflow Cron Last successful run
update-npm-dependencies.yml 0 8 * * 4 never
update-precommit-hooks.yml 0 8 * * 5 never

ℹ Manual-only by design

Workflow Last manual run Trigger
check-config-docs.yml long ago manual

Release-blocking gates — daily (release-gate cron 02:00 UTC)

Workflow Last activity Trigger Live badge
backwards-compatibility.yml last 30 days workflow_call, PR, push:main, release, schedule(0 2 * * 0), manual status
bandit.yml long ago PR, workflow_call, manual status
bearer.yml last 30 days PR, manual, workflow_call, schedule(0 4 * * *) status
checkov-scan.yml new workflow_call status
checkov.yml last 30 days manual, workflow_call status
codeql.yml last 30 days push:main, PR, schedule(45 5 * * 0), workflow_call, manual status
container-security.yml last 30 days workflow_call, manual status
devskim.yml last 30 days PR, manual, workflow_call, schedule(0 10 * * *) status
docker-multiarch-test.yml last 30 days workflow_call, manual status
dockle.yml last 30 days manual, workflow_call, schedule(0 10 * * 2) status
gitleaks-main.yml last 30 days workflow_call, manual status
grype.yml last 30 days workflow_call, manual status
hadolint.yml last 30 days PR, manual, workflow_call, schedule(0 9 * * 2) status
journal-data-integration.yml last 30 days workflow_call, manual, schedule(0 4 * * 1) status
npm-audit.yml last 30 days manual, workflow_call status
osv-scan-reusable.yml never workflow_call status
osv-scanner.yml last 30 days workflow_call, PR, merge_group, schedule(39 12 * * 1), manual status
owasp-zap-scan.yml last 30 days PR, workflow_call, manual status
retirejs.yml last 30 days manual, workflow_call, schedule(0 4 * * 1) status
security-headers-validation.yml last 30 days workflow_call, schedule(0 3 * * *), manual status
security-tests.yml last 30 days workflow_call, manual status
semgrep.yml last 30 days PR, workflow_call, manual status
zizmor-security.yml last 30 days PR, manual, workflow_call, schedule(0 9 * * 1) status

Release gates — release-time only

Workflow Last activity Trigger Live badge
check-env-vars.yml last 30 days PR, workflow_call, manual status
ci-gate.yml last 30 days workflow_call, manual status
compose-integration-test.yml last 30 days workflow_call, manual status
docker-publish.yml last 30 days workflow_call status
docker-tests.yml last 30 days PR, push:main, schedule(23 3 * * *), workflow_call, manual status
file-whitelist-check.yml last 30 days PR, workflow_call, manual status
mypy-type-check.yml last 30 days PR, workflow_call, manual status
notes-concurrency.yml last 30 days workflow_call, manual status
playwright-notes-tests.yml last 30 days PR, workflow_call, manual status
playwright-webkit-tests.yml last 30 days PR, workflow_call, manual, schedule(0 2 * * *) status
pre-commit.yml last 30 days PR, workflow_call, manual status
prerelease-docker.yml last 30 days workflow_call status
puppeteer-e2e-tests.yml last 30 days PR, workflow_call, manual, schedule(0 2 * * 0) status
responsive-ui-tests-enhanced.yml last 30 days workflow_call, manual status
security-file-write-check.yml last 30 days PR, workflow_call, manual status
validate-image-pinning.yml last 30 days PR, workflow_call, manual status
vulture-dead-code.yml last 30 days workflow_call, manual status

Scheduled (own cron)

Workflow Last activity Trigger Live badge
ci-health-report.yml last 30 days schedule(0 6 * * 1), manual, push:main status
compose-published-smoke.yml last 30 days manual, schedule(0 5 * * 1) status
fuzz.yml last 30 days schedule(0 0 * * 0), manual, PR status
gitleaks.yml last 30 days PR, manual, schedule(0 3 * * *) status
ossf-scorecard.yml last 30 days branch_protection_rule, schedule(0 8 * * 1), manual, push:main status
osv-scanner-scheduled.yml last 30 days push:main, schedule(41 21 * * 1), manual status
release-gate.yml last 30 days workflow_call, manual, schedule(0 2 * * *) status
sbom.yml last 30 days manual, schedule(0 10 * * 3), release status
security-mxss-browser-tests.yml last 30 days PR, manual, schedule(30 2 * * *) status
update-dependencies.yml last 30 days workflow_call, manual, schedule(0 8 * * 3) status
update-oldest-auto-merge-pr.yml last 30 days schedule(17,47 * * * *), manual status

PR / push checks

Workflow Last activity Trigger Live badge
advanced-search-reminder.yml last 30 days PR status
ai-code-reviewer.yml last 30 days PR-target status
check-workflow-status.yml last 30 days PR, manual status
ci-policy-tests.yml last 30 days PR, manual status
danger-zone-alert.yml last 30 days PR status
dependency-pr-checks.yml never PR-target status
dependency-review.yml last 30 days PR, manual status
e2e-research-test.yml last 30 days PR status
fastapi-migration-quality.yml last 30 days PR, manual status
gitleaks-rule-tests.yml last 30 days PR, push:main,refactor/fastapi-migration-phase1, manual status
labels-sync.yml last 30 days push:main, manual status
mcp-tests.yml last 30 days push:main, PR, manual status
milvus-tests.yml last 30 days push:main, PR, manual status
pr-triage.yml last 30 days PR, pull_request_review status
release-cleanup-tests.yml last 30 days PR, manual status
release-package-tests.yml last 30 days PR, manual status
release.yml last 30 days push:main, manual status
ui-full-shards.yml last 30 days PR, manual status
version_check.yml last 30 days push:main, manual status
welcome-first-time.yml last 30 days PR-target status
windows-database-tests.yml last 30 days PR, push:main, manual status

Repository-dispatch publishers

Workflow Last activity Trigger Live badge
publish.yml 1-3 months ago repo_dispatch status

Other

Workflow Last activity Trigger Live badge
issue-research.yml last 30 days issues status
ldr-research-reusable.yml never workflow_call status

Pending regeneration

Workflows added since the last dashboard regeneration. Regenerating (pdm run python scripts/generate_workflow_status.py) needs an authenticated gh, and it rewrites every "last activity" bucket on the page — noise a single-workflow PR shouldn't carry. This is the placeholder region that check-workflow-status.yml documents for that case. It sits outside the generated markers, so a regeneration preserves it verbatim: delete the row below by hand once the real one appears in the table above.

  • milvus-tests.yml — never run yet; push:main, PR, manual. Path-filtered to src/local_deep_research/vector_stores/**, tests/vector_stores/**, pyproject.toml, pdm.lock, .github/workflows/milvus-tests.yml. Self-gates until the Milvus backend and the milvus optional-dependency group land (#5331). Partial setups fail; only an entirely absent feature is skipped.

  • security-mxss-browser-tests.yml — real-browser mXSS regression tests for the markdown rendering path (#6295). PR, manual, schedule (daily 02:30 UTC). Path-filtered to the spec, its fixture, playwright.mxss.config.js, the Playwright package*.json, the sanitizer and service sources under test (web/static/js/security/**, web/static/js/services/ui.js, web/static/js/app.js), the root package*.json, and the workflow itself. Needs no application server, no auth and no secrets: the spec loads the production sanitizer modules and its fixture page from disk via setContent(), so it is safe to run on fork PRs.

  • windows-database-tests.yml — native Windows SQLCipher and file-I/O tests on Python 3.12 and 3.14; PR to main, push:main, manual. Path-filtered to database/settings sources, config paths, locked dependencies, the native test modules, runner, and workflow.

  • osv-scan-reusable.yml — shared workflow_call scanner used by osv-scanner.yml and osv-scanner-scheduled.yml. Verifies the native scanner binary and complete scan results before artifact and SARIF uploads. Its status is reported in the calling workflows.

  • rag-vector-scale.yml — manual large-collection latency benchmark for segmented FAISS (#7810). Flat and HNSW shards build a synthetic collection (1,000,000 vectors of 1,024 dimensions by default) without PDFs or an embedding model, and report per-document write time, search time and peak RSS. It is not called by release.yml and never runs on pull requests.

  • rag-index-scale.yml — required synthetic-PDF scale gate called by release.yml, with manual dispatch available. Separate flat and HNSW shards check bounded index writes, memory, search, rollback, deletion, staged rebuilding and encrypted storage using deterministic embeddings. The large workloads never run on pull requests. They run only through release.yml — on pushes to main or v*.*.* tags and on manual release dispatches, gated on should_release (a main push whose version already has a release skips them) — or through this workflow's own manual dispatch.

Offline performance assertions

performance-assertions.yml runs the available offline benchmark suites in a serial, bounded CI profile on relevant pull requests and main-branch changes. It explicitly enables integration checks and rejects missing, failed or skipped JUnit evidence and unverified measurement reports. When present, the original synthetic-PDF and vector-scale smoke cases cover flat and HNSW; larger release and manual workloads retain their existing profiles.

Each invocation stores results in a fresh run-* directory under its output path and updates ci-summary.json with the current run directory. Reports must match the requested area/profile and contain finite samples consistent with their counts and summaries. Existing manual-shard contracts join the selection when available. Native database, HTTP and RAG smoke measurements and retrieval quality reports are copied out of pytest temporary storage into the uploaded native/ results; database/RAG/HTTP use their fixed, asserted smoke settings, recorded in each report. Use their standalone CLIs for larger local workloads. Only numeric JSON and JUnit evidence is retained, rather than temporary databases.