Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.I4cTime/q-ring

NPM · @I4CTIME/Q-RING · SCANNED AUG 8

Quantum-inspired keyring for AI coding agents with superposition, entanglement, and tunneling.

Available components

+27 this week 50 Trust /100
Trust breakdown (6 categories)

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 Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 109 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to I4cTime/q-ring). View diagnostics → Pass
  • Clear OSI-approved license (AGPL-3.0-only).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need 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 the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

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.

npm · @i4ctime/q-ring

# add to Claude Code
claude mcp add i4ctime-q-ring -- npx -y @i4ctime/q-ring
# add to Codex CLI
codex mcp add i4ctime-q-ring -- npx -y @i4ctime/q-ring
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "i4ctime-q-ring": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@i4ctime/q-ring"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add i4ctime-q-ring --command npx --arg -y --arg @i4ctime/q-ring
# ~/.hermes/config.yaml
mcp_servers:
  i4ctime-q-ring:
    command: "npx"
    args: ["-y", "@i4ctime/q-ring"]
// mcp.json
{
  "mcpServers": {
    "i4ctime-q-ring": {
      "command": "npx",
      "args": [
        "-y",
        "@i4ctime/q-ring"
      ]
    }
  }
}
Changelog

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.

  • 7 Aug 26 +4
    • Known CVEs: partial → pass security
    • Stability: Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare. security
    • Security disclosure: fail → pass functional
    • Schema quality: Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess. functional
    • Dependency health: partial → 0.88 functional
  • 5 Aug 26 0
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Package version: 0.14.1 → 0.15.0 functional
  • 4 Aug 26 +8
    • Known CVEs: unverified → partial security
    • Dependency health: unverified → partial functional
  • 3 Aug 26 −8
    • Known CVEs: partial → unverified security
    • Dependency health: partial → unverified functional
    • Package version: 0.13.1 → 0.14.1 functional
    • Package version: 0.13.1 → 0.14.0 functional
  • 2 Aug 26 +23
    • Provenance: pass → unverified security
    • Install scripts: pass → unverified security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • The attested source repository moved: I4cTime/q-ring security
    • License: pass → unverified functional
    • Maintenance: pass → unverified functional
    • Dependency health: unverified → partial functional
    • Licence: AGPL-3.0-only functional
  • 1 Aug 26 −11
    • Known CVEs: partial → unverified security
    • Dependency health: partial → unverified functional
  • 31 Jul 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +35
    • Known CVEs: unverified → partial security
    • Provenance: unverified → pass security
    • Install scripts: unverified → pass security
    • The attested source repository moved: I4cTime/q-ring security
    • Security disclosure: unverified → fail functional
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • License: unverified → pass functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Licence: AGPL-3.0-only functional
Diagnostics

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 8 Aug 2026 · Analysed npm/@i4ctime/[email protected]

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 npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo I4cTime/q-ring
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/I4cTime/q-ring/.github/workflows/publish.yml@refs/tags/v0.15.0
Rekor log index 2347556893
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:5e21b5b99a0123fa6c37ea8bdb4841f03259a9cc7fa3e6ef7e1f415c202747227f4cf4815ea503993c5300e59a93f477f105932d9d8368f641bd78e64
Dependencies 109 packages
Packages resolved 109
Stale 30
Tree resolution Complete
MCP tools

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.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.