Aliyun fc provider

[lgxxabc]

---

[open-cla]

Contributor License Agreement

All contributors are covered by a CLA.

[devin-ai-integration]

Devin Review found 3 potential issues.

2 flags not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)

[devin-ai-integration]

🔴 Frozen installs block every benchmark run

With the downgraded specifiers, pnpm install --frozen-lockfile rejects the unchanged lockfile. The FC workflow and existing benchmark workflows stop before running any providers.

Learn more

The lockfile's root importer still records the previous specifiers, including @computesdk/declaw: 0.2.13, while the manifest now pins 0.2.12. The new install step and the existing install step both request a frozen lockfile. pnpm rejects a manifest whose dependency specifiers disagree with that lockfile, so no benchmark runs.

Example: The manifest requests @computesdk/declaw version 0.2.12, but the root lockfile importer still requests 0.2.13. A manual FC workflow dispatch fails during dependency installation rather than reaching sandbox creation.

Recommended fix: Restore the original dependency ranges if these downgrades were unintended, or regenerate and commit pnpm-lock.yaml for every changed range. Verify both workflows with pnpm install --frozen-lockfile.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🟥 Dispatch inputs execute shell commands

A dispatcher can embed shell syntax in iterations or concurrency. Direct interpolation executes it on the benchmark runner with the gateway and platform secrets available.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

🟨 Gateway credentials accepted over plaintext HTTP

When gatewayUrl uses HTTP, gatewayRequest sends its bearer secret without encryption. Network observers can capture the secret and impersonate the benchmark client.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[superagent-security]

Superagent found 1 security concern(s).

[superagent-security]

P1: Secret-bearing workflow uses mutable action tags without an explicit token permission boundary

New workflow runs mutable actions while exposing FC gateway secrets and leaves token permissions/checkout credentials at defaults.

Pin actions to SHAs, set least-privilege permissions, and disable checkout credential persistence.

AI prompt

Check if this security scanner issue is valid. If so, understand the root cause and fix it. If appropriate, update or add tests. Keep the change focused and preserve intended behavior.

<file name=".github/workflows/fc-benchmark.yml">
<violation number="1" location=".github/workflows/fc-benchmark.yml:36">
<priority>P1</priority>
<title>Secret-bearing workflow uses mutable action tags without an explicit token permission boundary</title>
<evidence>The new workflow checks out code with `actions/checkout@v4` at line 36 and later uses `pnpm/action-setup@v4`, `actions/setup-node@v4`, and `actions/upload-artifact@v4` by mutable tags. The same job exposes `BENCHMARKS_PLATFORM_API_KEY`, `ALIYUN_FC_GATEWAY_URL`, `ALIYUN_FC_GATEWAY_SECRET`, and `ALIYUN_FC_REGION` to the benchmark at lines 59-62, while the workflow declares no `permissions:` block and checkout does not disable credential persistence. A compromised or retagged action can therefore execute in this job's secret-bearing context and access the newly introduced gateway credentials and default GITHUB_TOKEN.</evidence>
<recommendation>Pin every `uses:` reference to the intended full commit SHA with a version comment, add a workflow-level `permissions: {}` (or the minimum required permissions), and set `persist-credentials: false` on checkout unless a later step demonstrably needs Git credentials. Keep secrets scoped only to the benchmark step.</recommendation>
</violation>
</file>