io.github.Judgment-Pack/judgment-pack
OCI · GHCR.IO/JUDGMENT-PACK/JUDGMENT-PACK:0.13.0 · SCANNED AUG 3
Offline JPS validator, conformance tester, and experimental evaluator over stdio MCP; keyless.
Available components
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 →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- CVE data not yet available for this package.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency-health data not yet available.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
- Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
- Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
- Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
oci · ghcr.io/judgment-pack/judgment-pack:0.13.0
claude mcp add judgment-pack-judgment-pack -- docker run --rm -i ghcr.io/judgment-pack/judgment-pack:0.13.0
codex mcp add judgment-pack-judgment-pack -- docker run --rm -i ghcr.io/judgment-pack/judgment-pack:0.13.0
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"judgment-pack-judgment-pack": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/judgment-pack/judgment-pack:0.13.0"
],
"enabled": true
}
}
} mcp_servers:
judgment-pack-judgment-pack:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/judgment-pack/judgment-pack:0.13.0"] {
"mcpServers": {
"judgment-pack-judgment-pack": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/judgment-pack/judgment-pack:0.13.0"
]
}
}
} 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.
- 3 Aug 26 9
First indexed and scored.
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 3 Aug 2026 · Analysed oci/ghcr.io/judgment-pack/judgment-pack:0.13.0
Provenance none
Ecosystem: oci · Outcome: none
Reason: no_attestation
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.
describe_runtime ~28
Report this runtime's version, the specification versions it supports, and the provenance of its bundled artifacts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
experimental_evaluate ~703
EXPERIMENTAL SURFACE (ADR-0007): apply the JPS Core §§7-8 resolution model to one conformant pack and one facts document, returning the §8.3 portable disposition (kind, outcomeId, reasons, handoff) and a trace. The disposition is serialized in its RFC 8785 canonical form; a refused evaluation reports its §8.4 error class and no disposition. Only a pack declaring specVersion 0.2.0-draft is evaluated: JPS §11 makes the value exact and requires an unedited 0.1.0-draft pack to be re-declared -- one edit, the specVersion string -- before an implementation claiming this draft evaluates it, so any other version is refused as pack-not-conformant in the preflight phase. The pack arrives either as text in "pack" or as a project decision id in "pack_id", which resolves through the jpack.json convention (ADR-0012); exactly one of the two is supplied, and supplying both is refused rather than given a precedence rule. Every payload echoes the evaluated pack's own id and version as packId and packVersion, read off the document that was evaluated. This is the one tool here that can write, and only where the project told it to (ADR-0018): in a project whose jpack.json declares an audit directory, each completed call appends one record to it -- the pack's identity and digest, the documents evaluated, and the disposition -- and in a project that declares none, nothing is written at all. This runtime's conformance claim is stated, in full and only, in the repository's CONFORMANCE.md; this description states no claim, and the payload carries a conformanceClaimReference member pointing at that file. Whatever that claim says, it is about this implementation and NOT about the pack you pass, the facts you supply, or whether acting on the returned disposition is correct, permitted, or safe (§3.5). It authorizes nothing, executes nothing, and this surface may change or be removed without compatibility promise.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | string | — | Optional tri-state evidence availability, as JSON text: an object mapping declared evidence-requirement ids to "present", "absent", or "unknown". An omitted id is unknown. Omit this key entirely to s… |
| facts | string | yes | One JSON facts document, as JSON text; fact.path pointers resolve against it. It is the NESTED document those pointers descend into: for the pointer /request/type write {"request":{"type":"data-acces… |
| pack | string | — | The JPS document to evaluate, as JSON text. It must have full document conformance; a non-conformant pack is refused. Mutually exclusive with pack_id. |
| pack_id | string | — | A decision id declared in the project's jpack.json, resolved to that pack's document. Mutually exclusive with pack; call list_packs for the available ids. |
| supported_extensions | array | — | Extension names this consumer supports. |
No output schema declared.
No examples provided.
get_example ~92
Return one bundled valid JPS example document by name, as JSON text, with its digest and byte size. These are version-pinned conformance fixtures, not authored templates; copy one into a document of your own to start authoring, then validate. Call list_examples for the available names.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The example name, as reported by list_examples (for example, minimal-expense-approval). |
No output schema declared.
No examples provided.
get_pack ~148
Return one pack document this project declares in its jpack.json, by its decision id, as JSON text, with the document's own id and version, its declared specVersion, its digest, and its byte size. The document is the project's own file, served unaltered and read-only; this tool stores nothing and returns nothing you did not already have on disk. Call list_packs for the available decision ids. The file is read through a reader rooted at the configuration's own directory, so a configured path that leaves that directory is refused rather than followed.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_id | string | yes | The project's decision id, as reported by list_packs (for example, expense-approval). |
No output schema declared.
No examples provided.
get_schema ~47
Return the exact bundled JPS JSON Schema for a specification version, with its digest and byte size.
| Name | Type | Req | Description |
|---|---|---|---|
| spec_version | string | — | Optional exact JPS version; defaults to the bundled draft. |
No output schema declared.
No examples provided.
list_examples ~56
List the bundled valid JPS example documents: version-pinned conformance fixtures the runtime embeds and digest-locks, offered read-only as starting points for authoring. They are not authored templates. Use get_example to fetch one by name.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_packs ~231
List the packs this project declares in its jpack.json, resolved: the project's decision id, the pack document's own id and version, the description, the ids of the evidence the pack requires, whether an instance matrix exists, and the project's non-normative hints about where each fact and each piece of evidence is held. The convention is this runtime's (ADR-0012) and is not part of the Judgment Pack Specification. Reading it is how you learn what a project can decide without fetching a pack; call get_pack for one document. The configuration is the JPACK_CONFIG file if that variable is set, otherwise jpack.json in the directory this server was launched in, and an absent configuration is an empty answer with an explanation rather than an error. The hints are the project's own words about where to look: this server holds no credential, opens no network connection, and never reads a source one names. Gathering those values is yours to do with your own access -- and a value you cannot source is reported unknown rather than guessed, so the pack can escalate instead of deciding on an invention.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
test_conformance ~68
Run a version-pinned JPS conformance corpus; the bundled corpus by default.
| Name | Type | Req | Description |
|---|---|---|---|
| spec_version | string | — | Optional exact JPS version; defaults to the bundled draft. |
| suite | string | — | Optional path to a local suite directory or manifest.json; omit for the bundled corpus. |
No output schema declared.
No examples provided.
validate ~69
Validate one JPS document for carrier, structural, and semantic conformance. It does not evaluate rules, choose an outcome, or authorize anything.
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | yes | The JPS document to validate, as JSON text. |
| through | string | — | Last validation layer to run; defaults to semantic. |
No output schema declared.
No examples provided.