Skip to content

chore(deps): update dependency octocode-mcp to v16 #776

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
renovate wants to merge 2 commits into
base: main
Choose a base branch
from
Open

chore(deps): update dependency octocode-mcp to v16 #776

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d6c5e5e
chore(deps): update dependency octocode-mcp to v16
renovate[bot] Jul 17, 2026
2d3b877
chore: allowlist AITech-8.2 for octocode-mcp v16 search/browse tools
danbarr Jul 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 15 additions & 1 deletion npx/octocode-mcp/spec.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,23 @@ metadata:

spec:
package: "octocode-mcp"
version: "15.0.2"
version: "16.0.0"

provenance:
# Monorepo with multiple packages; npm versions don't match git tags
repository_uri: "https://github.com/bgauryy/octocode-mcp"
repository_ref: "refs/heads/main"

security:
allowed_issues:
- code: "AITech-8.2"
reason: |
Flagged on ghSearchCode and localViewStructure, both read-only search/browse
tools that return results to the calling agent. This is inherent to
octocode-mcp's purpose as a GitHub + local code discovery server. The
equivalent tools in v15.0.2 (githubSearchCode, localViewStructure) exposed
the same read capability and passed the scan cleanly with 0 findings; the
v16.0.0 wording changes add local caching/proof-of-work phrasing (e.g.
"cache fetch", "clone", "structured entries[] output") that trips the YARA
heuristic without introducing a new data path. The scan's LLM analyzer,
run in the same pass, found no corroborating issue on either tool.
Loading