Add eliza-plugin-insumer

[douglasborthwick-crypto]

Registry Update Checklist

Registry:

• I've made the left side of the colon of JSON entry in index.json match the potential NPM package name
• I've used github not github.com
• There is no .git extension
• It's placed it alphabetically in the list
• I've dealt with commas properly so the list is still valid JSON

If not an eliza-plugins official repo, i.e. new plugin:

The plugin repo has:

• is publically accessible (not a private repo)
• uses main as it's default branch
• I have include elizaos-plugins in the topics in the GitHub repo settings. If the plugin is related to AI or crypto, please add those as topics as well.
• add simple description in github repo
• follows this convention
• an images/banner.jpg and images/logo.jpg and they
  • Use clear, high-resolution images (512x512 logo, 1200x675 banner)
  • Keep file sizes optimized (logo 18KB, banner 68KB)
• package.json has a agentConfig with pluginType: "elizaos:plugin:1.0.0" and pluginParameters

Plugin summary

eliza-plugin-insumer — On-chain wallet verification across 32 blockchains via InsumerAPI.

• npm: eliza-plugin-insumer
• GitHub: douglasborthwick-crypto/eliza-plugin-insumer
• Related issues: [Feature Request] Pre-transaction wallet reputation check for on-chain agent transfers elizaOS/eliza#6537

Summary by CodeRabbit

• Chores
  • Added new plugin integration to the registry.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

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: f16c5c69-963f-40fa-a560-d0ae40ca12e1

📥 Commits

Reviewing files that changed from the base of the PR and between 0ba410e and 7f59a65.

📒 Files selected for processing (1)

• index.json

✅ Files skipped from review due to trivial changes (1)

• index.json

---

Walkthrough

Added a new public plugin entry eliza-plugin-insumer to index.json, mapping it to github:douglasborthwick-crypto/eliza-plugin-insumer.

Changes

Cohort / File(s)	Summary
Plugin Registry index.json	Added a single mapping: "eliza-plugin-insumer": "github:douglasborthwick-crypto/eliza-plugin-insumer" (one-line addition).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 I hopped to the index, left a bright trail,
One tiny line, a bookmarked tail,
A gentle nudge, a plugin unfurled,
Quietly added to the plugins world,
Sniff, nibble, done — another small win.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add eliza-plugin-insumer' clearly and directly summarizes the main change — adding a new plugin registry entry.
Description check	✅ Passed	The description comprehensively follows the template with all registry checklist items marked complete, plugin summary provided, and links to npm and GitHub included.
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.}

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

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

Tip

CodeRabbit can scan for known vulnerabilities in your dependencies using OSV Scanner.

OSV Scanner will automatically detect and report security vulnerabilities in your project's dependencies. No additional configuration is required.

[greptile-apps]

npm package name mismatch

The registry key @insumer/plugin-insumer is a scoped npm package name, but the PR description links to the npm package as eliza-plugin-insumer (unscoped: https://www.npmjs.com/package/eliza-plugin-insumer).

The registry maps npm package names to GitHub repos, so if the package is only published under the unscoped name eliza-plugin-insumer, users installing via this registry entry using the scoped name @insumer/plugin-insumer will encounter a 404. The entry should match exactly the name under which the package is published on npm.

If the package is published under the @insumer scope, please confirm that @insumer/plugin-insumer is the correct npm package name. Otherwise, consider:

Suggested change

	"@insumer/plugin-insumer": "github:douglasborthwick-crypto/eliza-plugin-insumer",
	"eliza-plugin-insumer": "github:douglasborthwick-crypto/eliza-plugin-insumer",

[douglasborthwick-crypto]

Fixed in 37f33b7 — registry key is now eliza-plugin-insumer (unscoped), matching the published npm package.

[greptile-apps]

Unrelated change included

This PR repositions @elizaos/plugin-ATTPs from its previous location (between plugin-8004 and plugin-abstract) to here (between plugin-asterai and plugin-autocoder). While the new position is alphabetically correct, this change is not mentioned in the PR description and is unrelated to the addition of @insumer/plugin-insumer. Could you clarify if this reordering is intentional as part of this PR?

[douglasborthwick-crypto]

Fixed in 042c008 — plugin-ATTPs restored to its original position. The only diff vs upstream is the eliza-plugin-insumer addition.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@index.json`:
- Line 227: The registry entry for "@insumer/plugin-insumer" points to
"github:douglasborthwick-crypto/eliza-plugin-insumer" which cannot be found;
verify and correct the GitHub repo reference (confirm owner/name spelling and
public accessibility) or remove the entry if the repo is private or nonexistent,
and if corrected ensure the target repository contains a valid package.json and
plugin structure before updating the value in index.json (replace the
"github:..." string with the correct GitHub path or a validated package source).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5cbeff91-6d19-4c51-b302-45dc0723d365

📥 Commits

Reviewing files that changed from the base of the PR and between ef4930f and 054062a.

📒 Files selected for processing (1)

• index.json

[douglasborthwick-crypto]

Both issues flagged by the bots have been addressed:

• npm name mismatch (greptile): Fixed in 37f33b7 — registry key is now eliza-plugin-insumer matching the published npm package.
• Unrelated reorder of plugin-ATTPs (greptile): Reverted in 042c008.
• Repo accessibility (coderabbit): Repo is public and the package is live on npm (v1.0.5).

Ready for review when you get a chance.