The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Mar 27, 2026 4:13am

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

Merging this PR will not alter performance

✅ 16 untouched benchmarks

_{Comparing litellm_test_branch_03_26_2026_p1 (dfb5433) with main (b20cff8)}

Greptile Summary

This PR hardens the repository's GitHub Actions CI/CD workflows against injection attacks and over-privileged credentials, following recommendations from the zizmor static analysis tool. The core changes are: moving inline ${{ ... }} expressions to step-level env: blocks, pinning action refs to full commit SHAs, adding explicit permissions: blocks, and adding persist-credentials: false to actions/checkout calls.\n\nKey changes:\n- Inline expression injection risk eliminated across all changed workflows by routing values through env vars.\n- Action SHAs pinned in action.yml and dependabot cooldown periods added.\n- Explicit, minimal permissions: blocks added to 10+ workflows.\n- persist-credentials: false universally applied to actions/checkout.\n\nIssues found:\n- Breaking regression (P0): Both create-staging-branch and create-internal-dev-branch jobs in create_daily_staging_branch.yml call git push origin $BRANCH_NAME after setting persist-credentials: false. With no credential helper in place, these pushes will fail at runtime.\n- Silent caching regression (P1): In llm-translation-testing.yml, actions/cache was replaced with actions/cache/restore. The restore-only variant never writes an updated cache entry back after the job, so the Poetry dependency cache will grow stale over time.\n- Missing zizmor workflow: The PR description states "Includes a new zizmor action," but no new workflow file appears in the diff.

Confidence Score: 2/5

Not safe to merge as-is: create_daily_staging_branch.yml will fail at runtime due to broken git authentication after persist-credentials: false is applied to push jobs.

The security hardening intent is sound and most changes are correct. However, the persist-credentials: false change in create_daily_staging_branch.yml introduces a concrete runtime breakage: both branch-creation jobs call git push with no credential mechanism left in place, which will fail every scheduled run. This breaks a production workflow. The caching regression in llm-translation-testing.yml is a secondary (P1) issue. Together these prevent a safe merge.

.github/workflows/create_daily_staging_branch.yml (broken git push auth), .github/workflows/llm-translation-testing.yml (cache never saved)

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Workflow trigger] --> B[actions/checkout\npersist-credentials: false]
    B --> C{Job needs\ngit push?}
    C -- No --> D[✅ Read-only jobs\ntest-linting, test-litellm,\ncodspeed, codeql, etc.]
    C -- Yes --> E{Explicit auth\nconfigured?}
    E -- Yes --> F[✅ auto_update_price\nuses GH_TOKEN via gh CLI]
    E -- No --> G[❌ create_daily_staging_branch\ngit push fails — no credential helper]
    G --> H[403 Authentication Error\nat runtime]

_{Reviews (1): Last reviewed commit: "fix: address zizmor comments" | Re-trigger Greptile}