Add @scoutscore/plugin-eliza

[yaooooooooooooooo]

Add @scoutscore/plugin-eliza

Adds the ScoutScore trust intelligence plugin for ElizaOS.

Package: @scoutscore/plugin-eliza
Repo: https://github.com/scoutscore/plugin-scoutscore

What it does

ScoutScore gives ElizaOS agents the ability to verify x402 services before making payments. The plugin provides:

• 5 actions: CHECK_SERVICE_TRUST, CHECK_FIDELITY, SCAN_SKILL, BROWSE_LEADERBOARD, BATCH_SCORE_SERVICES
• 2 providers: trust-context (auto-injects trust data), trust-policy (payment guidelines)
• 1 evaluator: transaction-guard (blocks/warns on unsafe x402 payments)
• Background service: domain trust monitoring

It calls the ScoutScore API to score x402 services across 4 trust pillars (Contract Clarity, Availability, Response Fidelity, Identity Safety).

Checklist

• Only index.json modified
• Plugin repo is public: https://github.com/scoutscore/plugin-scoutscore
• Has elizaos-plugins GitHub topic
• Has logo (400x400) and banner (1280x640) images
• Plugin builds and exports default Plugin object
• Custom description (not placeholder)

Summary by CodeRabbit

• New Features
  • Added support for the Eliza plugin, expanding available plugin options.

Greptile Summary

This PR adds a single entry to the plugin registry, mapping the @scoutscore/plugin-eliza npm package to the github:scoutscore/plugin-scoutscore repository. The change is minimal, correctly formatted, and alphabetically sorted within index.json.

Key observations:

• The registry entry follows the correct "npm-package-name": "github:org/repo" format with no .git extension and using github: (not github.com).
• The alphabetical placement is correct — @scoutscore falls between @pyboom and @standujar.
• The npm package name (@scoutscore/plugin-eliza) differs from the GitHub repository name (plugin-scoutscore). This is permitted by the registry format, but the name field inside the repo's package.json must be @scoutscore/plugin-eliza for the elizaOS plugin loader to resolve it correctly during installation.

Confidence Score: 3/5

• The change is syntactically valid and properly formatted, but requires confirmation that the referenced repository's package.json declares the correct npm package name to avoid runtime plugin loader failures.
• The registry entry itself is correct in format and placement, earning it a baseline score. However, a critical unresolved dependency remains: the external repository's package.json must declare "name": "@scoutscore/plugin-eliza" for the elizaOS plugin loader to resolve the package correctly. Without author confirmation of this prerequisite, merging carries the risk that the plugin will fail to install or load despite the registry entry being correct.
• index.json (line 235) — requires author confirmation that the referenced GitHub repo's package.json contains the correct npm package name.

Sequence Diagram

sequenceDiagram
    participant User
    participant ElizaOS CLI
    participant Registry (index.json)
    participant GitHub (scoutscore/plugin-scoutscore)

    User->>ElizaOS CLI: elizaos install @scoutscore/plugin-eliza
    ElizaOS CLI->>Registry (index.json): lookup "@scoutscore/plugin-eliza"
    Registry (index.json)-->>ElizaOS CLI: "github:scoutscore/plugin-scoutscore"
    ElizaOS CLI->>GitHub (scoutscore/plugin-scoutscore): fetch package
    GitHub (scoutscore/plugin-scoutscore)-->>ElizaOS CLI: plugin source
    Note over ElizaOS CLI: Validates package.json "name" == "@scoutscore/plugin-eliza"
    ElizaOS CLI-->>User: Plugin installed & registered

Loading

_{Last reviewed commit: 543c8c0}

Greptile also left 1 inline comment on this PR.

_{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!}

[coderabbitai]

Walkthrough

Adds a new public plugin mapping entry to index.json, registering @scoutscore/plugin-eliza as an alias for the GitHub repository scoutscore/plugin-scoutscore. No other structural or functional changes present.

Changes

Cohort / File(s)	Summary
Plugin Mapping index.json	Added new public plugin mapping for @scoutscore/plugin-eliza pointing to github:scoutscore/plugin-scoutscore.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit hops with gleeful glee,
A new plugin joins the spree!
@scoutscore shines so bright and clear,
Fresh mapping magic appears here! 🐰✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely summarizes the main change: adding a new plugin entry to the registry.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The pull request provides a comprehensive description with detailed plugin functionality, proper checklist completion, and references to external validation.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.}

[greptile-apps]

Package name / repo name mismatch

The registry key on the left (@scoutscore/plugin-eliza) doesn't match the GitHub repository name (plugin-scoutscore). While diverging names are allowed by the registry format, the more important question is whether the package.json inside github:scoutscore/plugin-scoutscore declares "name": "@scoutscore/plugin-eliza".

If the repo's package.json has a different name (e.g., @scoutscore/plugin-scoutscore), elizaOS's dynamic plugin loader will fail to resolve the package correctly after installation, since it matches on the npm package name.

Please confirm that scoutscore/plugin-scoutscore/package.json contains:

"name": "@scoutscore/plugin-eliza"

[yaooooooooooooooo]

Confirmed — scoutscore/plugin-scoutscore/package.json declares "name": "@scoutscore/plugin-eliza". The npm package name matches the registry key.

https://github.com/scoutscore/plugin-scoutscore/blob/main/package.json#L2