[Code scan] Pin the reusable Gitee mirror workflow that receives the private key

Open Beginner friendly
#90 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
github-actions
Domain
ci-cd, security

Research direction

Start with .github/workflows/mirror_gitee.yml lines 9-13 and inspect the reusable workflow reference to deepmodeling/workflows. Pin that reference to an audited commit SHA or immutable release tag, then verify the workflow remains valid and the private-key handling path is unchanged.

Written by the indexing model from the issue text.

Description

This issue is a result of a Codex global code scan of deepmodeling/deepmodeling_sphinx at commit 156679fe55fc61e8ec3b1e9be8a45fde3567b9cb.

Problem

The Gitee mirror workflow calls a reusable workflow from deepmodeling/workflows at the mutable main ref while passing SYNC_GITEE_PRIVATE_KEY. Any change to that external repository's main branch changes the code that can handle this secret, without review in this repository.

Code references:

https://github.com/deepmodeling/deepmodeling_sphinx/blob/156679fe55fc61e8ec3b1e9be8a45fde3567b9cb/.github/workflows/mirror_gitee.yml#L9-L13

Impact

This widens the trust boundary for a private key. A benign breaking change, compromised workflow repository, or unreviewed update on main could immediately affect secret-handling behavior here.

Suggested fix

Pin the reusable workflow to an audited commit SHA or immutable release tag, and update it deliberately via reviewed PRs. If a floating ref is intentionally required, document the trust model and monitoring expectation in the workflow.

Dominant language
CSS
Stars
2
Forks
6
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from deepmodeling/deepmodeling_sphinx

All issues in deepmodeling/deepmodeling_sphinx

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.