Skip to content

Add @jhinresh/plugin-maiat-trust#311

Open
JhiNResH wants to merge 1 commit intoelizaos-plugins:mainfrom
JhiNResH:add-maiat-trust-plugin
Open

Add @jhinresh/plugin-maiat-trust#311
JhiNResH wants to merge 1 commit intoelizaos-plugins:mainfrom
JhiNResH:add-maiat-trust-plugin

Conversation

@JhiNResH
Copy link

@JhiNResH JhiNResH commented Mar 20, 2026

Maiat Trust — Trust scoring plugin for ElizaOS agents.

Package: @jhinresh/plugin-maiat-trust
Repo: https://github.com/JhiNResH/plugin-maiat-trust

Actions provided:

  • CHECK_TRUST — Behavioral trust score for agent wallets (18K+ agents indexed)
  • CHECK_TOKEN — Token safety check (honeypot, rug pull, liquidity risks)
  • TRUST_SWAP — Trust-verified swap quotes with safety checks
  • REPORT_OUTCOME — Feedback loop for trust score accuracy

Dependencies: @jhinresh/maiat-sdk

Built on Maiat Protocol (https://app.maiat.io) — trust infrastructure for the agent economy.

Summary by CodeRabbit

  • New Features
    • Added support for a new package: @jhinresh/plugin-maiat-trust.

Greptile Summary

This PR registers a single new entry in the plugin registry — @jhinresh/plugin-maiat-trust pointing to github:JhiNResH/plugin-maiat-trust — for a trust scoring plugin that provides CHECK_TRUST, CHECK_TOKEN, TRUST_SWAP, and REPORT_OUTCOME actions built on the Maiat Protocol.

Key concerns:

  • The target GitHub repository JhiNResH/plugin-maiat-trust could not be found as a publicly accessible repository in search results. Without a publicly reachable repository, users will be unable to install the plugin, making the registry entry non-functional.
  • The author's official Maiat Protocol repository (JhiNResH/maiat-protocol) publishes the ElizaOS integration under a different npm package name: @jhinresh/elizaos-plugin. The name @jhinresh/plugin-maiat-trust does not appear in any published package or repository that could be discovered publicly.
  • The alphabetical ordering in index.json is correct — the new entry is properly inserted between @esscrypt/plugin-polkadot and @kamiyo/eliza.

Confidence Score: 1/5

  • Not safe to merge — the referenced GitHub repository does not appear to exist publicly, and the registered package name differs from the author's known published ElizaOS plugin.
  • The sole change is a registry mapping, and its value (github:JhiNResH/plugin-maiat-trust) points to a repository that could not be verified as publicly accessible. Additionally, the package name @jhinresh/plugin-maiat-trust is inconsistent with the author's documented ElizaOS package (@jhinresh/elizaos-plugin). A broken or missing repository would render the registry entry unusable for any ElizaOS user trying to install this plugin.
  • index.json — the new registry entry at line 227 needs the GitHub repository URL to be verified as publicly accessible before merging.

Important Files Changed

Filename Overview
index.json Adds a single registry entry for @jhinresh/plugin-maiat-trustgithub:JhiNResH/plugin-maiat-trust; the target repository does not appear to be publicly accessible and the package name does not match the author's known published ElizaOS plugin (@jhinresh/elizaos-plugin).

Sequence Diagram

sequenceDiagram
    participant User as ElizaOS User
    participant Registry as Plugin Registry (index.json)
    participant GH as github:JhiNResH/plugin-maiat-trust
    participant SDK as @jhinresh/maiat-sdk
    participant API as Maiat Protocol API (app.maiat.io)

    User->>Registry: npm install @jhinresh/plugin-maiat-trust
    Registry->>GH: Resolve github:JhiNResH/plugin-maiat-trust
    Note over GH: ⚠️ Repository not found publicly
    GH-->>User: Resolution error (if repo is missing/private)

    Note over User,API: Expected happy path (if repo exists)
    GH-->>User: Plugin source downloaded
    User->>SDK: Plugin loads @jhinresh/maiat-sdk
    SDK->>API: CHECK_TRUST / CHECK_TOKEN / TRUST_SWAP / REPORT_OUTCOME
    API-->>SDK: Trust score / token safety / swap quote
    SDK-->>User: Action result returned to agent
Loading

Last reviewed commit: "Add @jhinresh/plugin..."

Greptile also left 1 inline comment on this PR.

(4/5) You can add custom instructions or style guidelines for the agent here!

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 20, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c24d87a9-64e5-4f8b-a174-0717402eaea0

📥 Commits

Reviewing files that changed from the base of the PR and between ce554dd and 2358f28.

📒 Files selected for processing (1)
  • index.json

Walkthrough

A new package entry for @jhinresh/plugin-maiat-trust was added to the package registry index, mapping it to its GitHub repository location (github:JhiNResH/plugin-maiat-trust).

Changes

Cohort / File(s) Summary
Package Registry Update
index.json
Added new package entry mapping @jhinresh/plugin-maiat-trust to github:JhiNResH/plugin-maiat-trust

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A new plugin joins the garden so bright,
Maiat trust blooms in the registry light,
One line of code, a registry's cheer,
The ecosystem expands, year after year! 🌱

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description provides plugin details and functionality but does not follow the required Registry Update Checklist template with its mandatory checkboxes and validation criteria. Replace the current description with the Registry Update Checklist template and complete all required checkboxes to verify compliance with registry standards.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately reflects the main change: adding a new package entry for @jhinresh/plugin-maiat-trust to the registry.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

Important

Merge conflicts detected (Beta)

  • Resolve merge conflict in branch add-maiat-trust-plugin
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

CodeRabbit can use OpenGrep to find security vulnerabilities and bugs across 17+ programming languages.

OpenGrep is compatible with Semgrep configurations. Add an opengrep.yml or semgrep.yml configuration file to your project to enable OpenGrep analysis.

"@elizaos/plugin-zytron": "github:zypher-network/plugin-zytron",
"@erdgecrawl/plugin-base-signals": "github:erdGeclaw/plugin-base-signals",
"@esscrypt/plugin-polkadot": "github:Esscrypt/plugin-polkadot",
"@jhinresh/plugin-maiat-trust": "github:JhiNResH/plugin-maiat-trust",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Package name mismatch with published npm package

The key registered here is @jhinresh/plugin-maiat-trust pointing to github:JhiNResH/plugin-maiat-trust, but the official Maiat Protocol repository (JhiNResH/maiat-protocol) lists the ElizaOS integration as a different package: @jhinresh/elizaos-plugin (published at npmjs.com/package/@jhinresh/elizaos-plugin).

The plugin-maiat-trust repository was not found in public search results — it does not appear to exist as a publicly accessible GitHub repository, nor as a published npm package under this name. If the target repo is missing or private, anyone attempting to install this plugin will get a resolution error.

Please verify that github:JhiNResH/plugin-maiat-trust is publicly accessible, and clarify whether this is a separate new repository from the maiat-protocol monorepo. If the intent is to register the existing ElizaOS plugin, the entry should likely be:

"@jhinresh/elizaos-plugin": "github:JhiNResH/maiat-protocol#main:packages/elizaos-plugin"

or wherever the package lives inside the monorepo.

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.

1 participant