Skip to content

Conversation

@aarlaud
Copy link
Contributor

@aarlaud aarlaud commented Nov 26, 2025

Pull Request Submission Checklist

  • Follows CONTRIBUTING guidelines
  • Commit messages
    are release-note ready, emphasizing
    what was changed, not how.
  • Includes detailed description of changes
  • Contains risk assessment (Low | Medium | High)
  • Highlights breaking API changes (if applicable)
  • Links to automated tests covering new functionality
  • Includes manual testing instructions (if necessary)
  • Updates relevant GitBook documentation (PR link: ___)
  • Includes product update to be announced in the next stable release notes

What does this PR do?

Adds experimental mcp-scan command via dedicated cli extension.

Where should the reviewer start?

https://github.com/snyk/cli-extension-mcp-scan

How should this be manually tested?

mcp-scan --experimental

What's the product update that needs to be communicated to CLI users?

mcp-scan as part of evo.

Risk assessment (Low | Medium | High)?

Low

@aarlaud aarlaud force-pushed the feat/add-mcp-scan-workflow branch from d426edc to 4a26f83 Compare November 26, 2025 17:03
@aarlaud
Copy link
Contributor Author

aarlaud commented Nov 26, 2025

depends on snyk/go-application-framework#491

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants