Sheriff
OCI · GHCR.IO/RYANSMITH4/SHERIFF-MCP:1.0.2
MCP server for fixing static analysis issues from SARIF reports with AI agents
Available components
Last scanned (14 hours ago)
Scores higher than 0% of OCI servers
Category Testing and QA
Recent critical change
CVE-2026-12087 affects this package (18 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency94
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ryansmith4/sheriff-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Maintenance history not yet determined.Unverified
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
Checks we ran (5)
- Known CVEs
- Source repository
- Provenance
- License
- Security disclosure
Checks we could not complete (9)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityNo malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Install scripts in Supply Chain SecurityInstall-script risk not yet assessed.
- Dependency health in Supply Chain SecurityDependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.
- Maintenance in Provenance & TransparencyMaintenance history not yet determined.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Oct 26 0
- CVE-2025-69720 no longer affects this package ▲ security
- 24 Oct 26 0
- CVE-2026-12087 no longer affects this package ▲ security
- CVE-2026-5450 no longer affects this package ▲ security
- CVE-2026-8376 no longer affects this package ▲ security
- CVE-2026-42496 no longer affects this package ▲ security
- CVE-2026-57433 no longer affects this package ▲ security
- CVE-2026-13221 no longer affects this package ▲ security
- 18 Oct 26 0
- CVE-2026-12087 affects this package: high ▼ critical
- CVE-2026-13221 affects this package: high ▼ critical
- CVE-2026-5450 affects this package: high ▼ critical
- CVE-2026-42010 affects this package: high ▼ critical
- CVE-2025-69720 affects this package: high ▼ critical
- CVE-2026-8376 affects this package: high ▼ critical
- CVE-2026-33845 affects this package: high ▼ critical
- CVE-2026-57433 affects this package: high ▼ critical
- CVE-2026-42496 affects this package: high ▼ critical
- 17 Oct 26 0
- CVE-2026-8925 affects this package: none ▼ critical
- CVE-2026-33845 affects this package: none ▼ critical
- CVE-2026-13221 affects this package: none ▼ critical
- CVE-2026-8927 affects this package: none ▼ critical
- CVE-2026-8924 affects this package: none ▼ critical
- CVE-2026-34182 affects this package: none ▼ critical
- CVE-2026-10536 affects this package: none ▼ critical
- CVE-2026-18924 affects this package: none ▼ critical
- CVE-2026-8376 affects this package: none ▼ critical
- CVE-2026-31789 affects this package: none ▼ critical
- CVE-2026-5450 affects this package: none ▼ critical
- CVE-2026-42010 affects this package: none ▼ critical
- CVE-2026-42496 affects this package: none ▼ critical
- CVE-2026-11856 affects this package: none ▼ critical
- CVE-2026-12087 affects this package: none ▼ critical
- CVE-2026-75803 affects this package: none ▼ critical
- CVE-2026-57433 affects this package: none ▼ critical
- CVE-2025-69720 affects this package: none ▼ critical
- 16 Oct 26 0
- CVE-2026-8925 affects this package: none ▼ critical
- CVE-2026-33845 affects this package: none ▼ critical
- CVE-2026-13221 affects this package: none ▼ critical
- CVE-2026-8927 affects this package: none ▼ critical
- CVE-2026-8924 affects this package: none ▼ critical
- CVE-2026-34182 affects this package: none ▼ critical
- CVE-2026-10536 affects this package: none ▼ critical
- CVE-2026-18924 affects this package: none ▼ critical
- CVE-2026-8376 affects this package: none ▼ critical
- CVE-2026-31789 affects this package: none ▼ critical
- CVE-2026-5450 affects this package: none ▼ critical
- CVE-2026-42010 affects this package: none ▼ critical
- CVE-2026-42496 affects this package: none ▼ critical
- CVE-2026-11856 affects this package: none ▼ critical
- CVE-2026-12087 affects this package: none ▼ critical
- CVE-2026-75803 affects this package: none ▼ critical
- CVE-2026-57433 affects this package: none ▼ critical
- CVE-2025-69720 affects this package: none ▼ critical
- 15 Oct 26 0
- CVE-2026-8925 affects this package: none ▼ critical
- CVE-2026-33845 affects this package: none ▼ critical
- CVE-2026-13221 affects this package: none ▼ critical
- CVE-2026-8927 affects this package: none ▼ critical
- CVE-2026-8924 affects this package: none ▼ critical
- CVE-2026-34182 affects this package: none ▼ critical
- CVE-2026-10536 affects this package: none ▼ critical
- CVE-2026-18924 affects this package: none ▼ critical
- CVE-2026-8376 affects this package: none ▼ critical
- CVE-2026-31789 affects this package: none ▼ critical
- CVE-2026-5450 affects this package: none ▼ critical
- CVE-2026-42010 affects this package: none ▼ critical
- CVE-2026-42496 affects this package: none ▼ critical
- CVE-2026-11856 affects this package: none ▼ critical
- CVE-2026-12087 affects this package: none ▼ critical
- CVE-2026-75803 affects this package: none ▼ critical
- CVE-2026-57433 affects this package: none ▼ critical
- CVE-2025-69720 affects this package: none ▼ critical
- 14 Oct 26 0
- CVE-2026-8925 affects this package: none ▼ critical
- CVE-2026-33845 affects this package: none ▼ critical
- CVE-2026-13221 affects this package: none ▼ critical
- CVE-2026-8927 affects this package: none ▼ critical
- CVE-2026-8924 affects this package: none ▼ critical
- CVE-2026-34182 affects this package: none ▼ critical
- CVE-2026-10536 affects this package: none ▼ critical
- CVE-2026-18924 affects this package: none ▼ critical
- CVE-2026-8376 affects this package: none ▼ critical
- CVE-2026-31789 affects this package: none ▼ critical
- CVE-2026-5450 affects this package: none ▼ critical
- CVE-2026-42010 affects this package: none ▼ critical
- CVE-2026-42496 affects this package: none ▼ critical
- CVE-2026-11856 affects this package: none ▼ critical
- CVE-2026-12087 affects this package: none ▼ critical
- CVE-2026-75803 affects this package: none ▼ critical
- CVE-2026-57433 affects this package: none ▼ critical
- CVE-2025-69720 affects this package: none ▼ critical
- 13 Oct 26 0
- CVE-2026-8925 affects this package: none ▼ critical
- CVE-2026-33845 affects this package: none ▼ critical
- CVE-2026-13221 affects this package: none ▼ critical
- CVE-2026-8927 affects this package: none ▼ critical
- CVE-2026-8924 affects this package: none ▼ critical
- CVE-2026-34182 affects this package: none ▼ critical
- CVE-2026-10536 affects this package: none ▼ critical
- CVE-2026-18924 affects this package: none ▼ critical
- CVE-2026-8376 affects this package: none ▼ critical
- CVE-2026-31789 affects this package: none ▼ critical
- CVE-2026-5450 affects this package: none ▼ critical
- CVE-2026-42010 affects this package: none ▼ critical
- CVE-2026-42496 affects this package: none ▼ critical
- CVE-2026-11856 affects this package: none ▼ critical
- CVE-2026-12087 affects this package: none ▼ critical
- CVE-2026-75803 affects this package: none ▼ critical
- CVE-2026-57433 affects this package: none ▼ critical
- CVE-2025-69720 affects this package: none ▼ critical
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed oci/ghcr.io/ryansmith4/sheriff-mcp:1.0.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | ryansmith4/sheriff-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ryansmith4/sheriff-mcp/.github/workflows/release.yml@refs/tags/v1.0.2 |
| Rekor log index | 1173958402 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:99eca496c87625a4d312836c7fec5943c848d9249a70b1692a7a780005f368c2 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 89 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| UBUNTU-CVE-2026-102473 | CVE-2026-102473 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | no |
| UBUNTU-CVE-2026-102474 | CVE-2026-102474 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | no |
| UBUNTU-CVE-2026-2219 | CVE-2026-2219 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| USN-8249-1 | CVE-2026-2219 | none | yes | |
| UBUNTU-CVE-2026-41991 | CVE-2026-41991 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N | yes |
| UBUNTU-CVE-2026-41992 | CVE-2026-41992 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| USN-8512-1 | CVE-2026-41991 | none | yes | |
| GHSA-7hhh-6rmp-j9qf | CVE-2026-89425 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-p6pp-m3f8-5c89 | CVE-2026-89407 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-r7wm-3cxj-wff9 | CVE-2026-68494 | high | yes | |
| GHSA-3pjw-73gf-8qr5 | CVE-2026-59888 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-5gvw-p9qm-jgwh | CVE-2026-59889 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-5hh8-q8hv-fr38 | CVE-2026-54517 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-5jmj-h7xm-6q6v | CVE-2026-54515 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-9fxm-vc8v-hj55 | CVE-2026-54516 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-cxp5-3px4-pw24 | CVE-2026-91777 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-gx83-3vf8-gh7j | CVE-2026-83557 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L | yes |
| GHSA-hgj6-7826-r7m5 | CVE-2026-54514 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-j3rv-43j4-c7qm | CVE-2026-54512 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-mhm7-754m-9p8w | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N | yes | |
| GHSA-q4xh-88c3-wmh7 | CVE-2026-68497 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-rcqc-6cw3-h962 | CVE-2026-54518 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-rmj7-2vxq-3g9f | CVE-2026-54513 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-vvgp-rfg2-7rr6 | CVE-2026-77310 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-wjgm-6hv5-3cvf | CVE-2026-19032 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-wv8q-qhhj-9h54 | CVE-2026-91776 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| UBUNTU-CVE-2026-54369 | CVE-2026-54369 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N | no |
| UBUNTU-CVE-2026-54370 | CVE-2026-54370 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | no |
| UBUNTU-CVE-2026-4878 | CVE-2026-4878 | high | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H | yes |
| USN-8193-1 | CVE-2026-4878 | none | yes | |
| UBUNTU-CVE-2026-33845 | CVE-2026-33845 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H | yes |
| UBUNTU-CVE-2026-33846 | CVE-2026-33846 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| UBUNTU-CVE-2026-3832 | CVE-2026-3832 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| UBUNTU-CVE-2026-3833 | CVE-2026-3833 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| UBUNTU-CVE-2026-42009 | CVE-2026-42009 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| UBUNTU-CVE-2026-42010 | CVE-2026-42010 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| UBUNTU-CVE-2026-42011 | CVE-2026-42011 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| UBUNTU-CVE-2026-42012 | CVE-2026-42012 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N | yes |
| UBUNTU-CVE-2026-42013 | CVE-2026-42013 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N | yes |
| UBUNTU-CVE-2026-42014 | CVE-2026-42014 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H | yes |
| UBUNTU-CVE-2026-42015 | CVE-2026-42015 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| UBUNTU-CVE-2026-5260 | CVE-2026-5260 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H | yes |
| UBUNTU-CVE-2026-5419 | CVE-2026-5419 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| UBUNTU-CVE-2026-67693 | CVE-2026-67693 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N | no |
| UBUNTU-CVE-2026-88647 | CVE-2026-88647 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N | no |
| UBUNTU-CVE-2026-88648 | CVE-2026-88648 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N | no |
| UBUNTU-CVE-2026-95184 | CVE-2026-95184 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| UBUNTU-CVE-2026-95209 | CVE-2026-95209 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| UBUNTU-CVE-2026-95210 | CVE-2026-95210 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | no |
| USN-8284-1 | none | yes |
Showing 50 of 89 vulnerabilities.
Background: What a vulnerability scan can and cannot prove →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.
How do I install the Sheriff MCP server?
Sheriff runs locally as a container image, launched with docker run --rm -i ghcr.io/ryansmith4/sheriff-mcp:1.0.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/ryansmith4/sheriff-mcp:1.0.2
claude mcp add ryansmith4-sheriff-mcp -- docker run --rm -i ghcr.io/ryansmith4/sheriff-mcp:1.0.2
What is the Sheriff MCP server?
Sheriff is an MCP server listed in the public MCP registry as io.github.ryansmith4/sheriff-mcp. MCP server for fixing static analysis issues from SARIF reports with AI agents. This page covers its container image (ghcr.io/ryansmith4/sheriff-mcp:1.0.2).
Is the Sheriff MCP server still maintained?
Sheriff is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Sheriff MCP server under?
Sheriff declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.