Skip to content

Commit c48ffb0

Browse files
authored
Merge pull request #31 from lirantal/fix/openssf-agent-updates-to-new-qodo-command-version
fix: update openssf scorecard fixer agent
2 parents 57e9c2d + 49041e7 commit c48ffb0

File tree

2 files changed

+5
-27
lines changed

2 files changed

+5
-27
lines changed

agents/openssf-scorecard-fixer/README.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@ Pre-requisite for running this agent includes:
88

99
- GitHub Personal Access Token (PAT) with `repo` scope
1010
- Docker installed and running
11-
- GitHub MCP Server running locally
1211
- GitHub CLI tool (`gh`) installed
1312
- OpenSSF Scorecard CLI tool installed
1413
- Qodo Command installed globally (`npm install -g @qodo/command`)

agents/openssf-scorecard-fixer/agent.yaml

Lines changed: 5 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
version: "1.0"
1+
/version: "1.0"
22

33
commands:
44
openssf-scorecard-fixer:
@@ -45,30 +45,10 @@ commands:
4545
- git
4646
- filesystem
4747
- shell
48-
- github
4948
- web_search
5049

5150
execution_strategy: plan
5251

53-
mcpServers: |
54-
{
55-
"shell": {
56-
"command": "uvx",
57-
"args": [
58-
"mcp-shell-server"
59-
],
60-
"env": {
61-
"ALLOW_COMMANDS": "scorecard,docker,env,ls,cat,pwd,rg,wc,touch,find,mkdir,rm,cp,mv,npm,npx,jest,mocha,ts-node,tsc,node,jq,echo,test,diff,sed,awk,git,cd,exit,yarn,grep,gh,base64,curl,python3,python,pip,pip3,which,whoami,id,uname,date,head,tail,sort,uniq,tr,cut,xargs,sleep"
62-
}
63-
},
64-
"github": {
65-
"url": "https://api.githubcopilot.com/mcp/",
66-
"headers": {
67-
"Authorization": "Bearer ${GITHUB_PERSONAL_ACCESS_TOKEN}"
68-
}
69-
}
70-
}
71-
7252
instructions: |
7353
You are an expert product security engineer with a focus on improving the security posture of open source projects. Your task is to automatically address and fix issues raised by the OpenSSF Scorecard tool, which identifies security vulnerabilities and best practices in code repositories. You should analyze each issue, leverage tools at your disposal, determine the appropriate action, and execute it to enhance the security of the codebase.
7454
@@ -77,13 +57,12 @@ commands:
7757
0. **Your Tool Box**
7858
7959
- You can find the GitHub Personal Access token in the environment variable GITHUB_AUTH_TOKEN
80-
- For all GitHub operations, prefer using the GitHub CLI (`gh`) commands over the GitHub MCP server when encountering API limitations
81-
- If GitHub MCP server operations fail, clone the repository locally using `git clone` and work with local files
60+
- For all GitHub operations, use the GitHub CLI (`gh`)
8261
- To run the OpenSSF Scorecard tool, use: `scorecard --repo=<INSERT REPO> --show-details` (replace with the repository from the `repo` argument)
8362
- You can get information from URLs using the web_fetch tool
8463
- For base64 decoding, use: `echo "<base64_string>" | base64 -d` or Node.js: `node -e "console.log(Buffer.from('<base64>', 'base64').toString())"`
8564
- Always verify GitHub CLI authentication with `gh auth status` before attempting operations
86-
- Use `gh api` for direct GitHub API calls when the MCP server fails
65+
- Use `gh api` for direct GitHub API calls if needed
8766
- Respect the command arguments: create_pr, enable_branch_protection, fix_vulnerabilities, base_branch, branch_name
8867
8968
1. **Issue Analysis**
@@ -99,7 +78,7 @@ commands:
9978
10079
For Each Issue:
10180
- Execute the most appropriate fix to address the issue
102-
- If GitHub MCP server operations fail, use this fallback strategy:
81+
- You may use the following strategy to work with a local git cloned repository if the `gh` CLI commands fail:
10382
1. Clone the repository locally: `git clone <repo_url>`
10483
2. Create a new branch: `git checkout -b <branch_name>` (use the branch_name argument)
10584
3. Make necessary changes to local files
@@ -175,4 +154,4 @@ commands:
175154
- List of issues addressed with specific actions taken
176155
- Any issues that could not be resolved and why
177156
- Links to created pull requests (if any)
178-
- Recommendations for ongoing security maintenance
157+
- Recommendations for ongoing security maintenance

0 commit comments

Comments
 (0)