Add @jhinresh/plugin-maiat-trust#311
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughA new package entry for Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Important Merge conflicts detected (Beta)
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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. Comment Tip CodeRabbit can use OpenGrep to find security vulnerabilities and bugs across 17+ programming languages.OpenGrep is compatible with Semgrep configurations. Add an |
| "@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", |
There was a problem hiding this comment.
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.
Maiat Trust — Trust scoring plugin for ElizaOS agents.
Package:
@jhinresh/plugin-maiat-trustRepo: 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 checksREPORT_OUTCOME— Feedback loop for trust score accuracyDependencies:
@jhinresh/maiat-sdkBuilt on Maiat Protocol (https://app.maiat.io) — trust infrastructure for the agent economy.
Summary by CodeRabbit
@jhinresh/plugin-maiat-trust.Greptile Summary
This PR registers a single new entry in the plugin registry —
@jhinresh/plugin-maiat-trustpointing togithub:JhiNResH/plugin-maiat-trust— for a trust scoring plugin that providesCHECK_TRUST,CHECK_TOKEN,TRUST_SWAP, andREPORT_OUTCOMEactions built on the Maiat Protocol.Key concerns:
JhiNResH/plugin-maiat-trustcould 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.JhiNResH/maiat-protocol) publishes the ElizaOS integration under a different npm package name:@jhinresh/elizaos-plugin. The name@jhinresh/plugin-maiat-trustdoes not appear in any published package or repository that could be discovered publicly.index.jsonis correct — the new entry is properly inserted between@esscrypt/plugin-polkadotand@kamiyo/eliza.Confidence Score: 1/5
github:JhiNResH/plugin-maiat-trust) points to a repository that could not be verified as publicly accessible. Additionally, the package name@jhinresh/plugin-maiat-trustis 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.Important Files Changed
@jhinresh/plugin-maiat-trust→github: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 agentLast reviewed commit: "Add @jhinresh/plugin..."
(4/5) You can add custom instructions or style guidelines for the agent here!