Armory
Source

Leaderboard

Scored on public signals; components with none are listed as Unranked · Formula

RankScoreComponentDescriptionEvidenceLast commitInstall
138.412omnidotdev-persona-jsonidentity · authUse when a non-human actor needs a portable, machine-readable identity document that travels with it between systems.3 starsNo one-command install · Source
254.833paymanai-sigilumidentity · authUse when an agent's identity has to leave an auditable trail rather than just gate a request.9 starsNo one-command install · Source
357.245amirf194-wingfootidentity · authUse when your agent keeps getting blocked by sites and you need it to present a verifiable bot identity and be told why it failed.7 stars · 1 forkNo one-command install · Source
458.185sunilp-aipidentity · authUse when an agent's identity must carry across both MCP and agent-to-agent calls under one delegable scheme.6 stars · 2 forksNo one-command install · Source
559.040imphillip-soultavernidentity · authUse when you have character cards from the roleplay ecosystem and want them as SOUL.md personas an agent runtime can load.13 starsNo one-command install · Source
659.854chrisdbaldwin-masquesidentity · authUse when an agent needs to put on a temporary role — a bundle of intent, context and lens — for one task and take it off afterwards.14 starsNo one-command install · Source
764.883intelliger-ai-oatiidentity · authUse when an agent's authority, and every action it took under that authority, must be verifiable after the fact.13 stars · 1 forkNo one-command install · Source
869.786clawsouls-soulspecidentity · authUse when you want one file to define an agent's persistent identity in a way any compatible runtime can load.21 stars · 1 forkNo one-command install · Source
972.722kanoniv-agent-authidentity · authUse when authority must be handed down a chain of agents and each hop stays provable.15 stars · 4 forksNo one-command install · Source
1073.383soth-ai-agentfacts-pyidentity · authUse when an agent should publish verifiable facts about itself — capabilities, provenance, operator — that another party can check.33 stars · 1 forkNo one-command install · Source
1175.153authsec-aiidentity · authUse when agent-to-agent calls need mutual authentication and a place to keep the agent's own secrets.16 stars · 6 forksNo one-command install · Source
1277.331mandarwagh9-machineauthidentity · authUse when agents need to reach APIs and tools with their own credentials and permission scopes.61 stars · 1 forkNo one-command install · Source
1379.229alien-id-agent-ididentity · authUse when each agent needs its own keypair so its actions can be signed and later attributed.38 stars · 3 forksNo one-command install · Source
1480.555newtype-ai-nitidentity · authUse when you want an agent's identity to be versioned and inspectable the way a repository is.128 stars · 1 forkNo one-command install · Source
1581.185auth0-auth0-ai-jsidentity · authUse when an agent must act on a user's behalf against a third-party API with the user's own consent and scope.15 stars · 13 forksNo one-command install · Source
1682.544vouch-protocol-vouchidentity · authUse when agents acting in the world need identities that can be vouched for and held accountable afterwards.27 stars · 13 forksNo one-command install · Source
1783.917siddhant-k-code-agentic-authzidentity · authUse when 'which agent may do what, to whose data' needs to be a policy decision rather than a code branch.65 stars · 4 forksNo one-command install · Source
1884.840agentcommunity-agent-identity-discoveryidentity · authUse when you want to find an agent's interface starting from nothing but a domain name.47 stars · 8 forksNo one-command install · Source
1985.034deeptrail-deepsecureidentity · authUse when agents move from prototype to production and their identities, secrets and access need managing centrally.52 stars · 7 forksNo one-command install · Source
2087.545vestauthidentity · authUse when an agent needs to authenticate as itself to services, without you hand-rolling keys and rotation.166 stars · 4 forksNo one-command install · Source
2188.551opena2a-agent-identity-managementidentity · authUse when non-human identities need the same lifecycle a workforce IAM gives people — issue, authorize, audit, revoke.59 stars · 18 forksNo one-command install · Source
2288.673gebruder-wirkenidentity · authUse when autonomous agents need one gateway that holds their credentials, isolates them per channel, and logs every session.171 stars · 5 forksNo one-command install · Source
2388.683agentrhq-authsomeidentity · authUse when agents must stay logged in to third-party services without ever seeing your credentials.87 stars · 9 forksNo one-command install · Source
2490.247character-card-spec-v3identity · authUse when authoring an agent persona against the current character-card standard, with lorebooks, assets and decorators.109 stars · 11 forksStaleNo one-command install · Source
2591.688agentmail-to-agentmail-toolkitidentity · authUse when an agent needs its own email address so people and systems can reach it, and it can act on what arrives.98 stars · 26 forksNo one-command install · Source
2692.701highflame-ai-zeroididentity · authUse when a fleet of autonomous agents needs issued identities with a lifecycle — created, rotated and revoked.163 stars · 18 forksNo one-command install · Source
2793.844cloudflare-web-bot-authidentity · authUse when a website has to be able to tell that a request really came from your agent and not from someone impersonating it.157 stars · 40 forksNo one-command install · Source
2893.959character-card-spec-v2identity · authUse when reading or writing the character-card files that the roleplay-agent ecosystem actually ships, including the PNG-embedded variant.188 stars · 29 forksStaleNo one-command install · Source
2995.782agntcy-oasfidentity · authUse when agents must describe themselves to other systems in a common schema so they can be catalogued, discovered and verified.332 stars · 47 forksNo one-command install · Source

Score colour shows how many signals stand behind it, never how good it is: amber, three or more; dimmer amber, two; grey, one. The Evidence column names them.

Stars, forks and last commit are as GitHub reported them when Armory last read each repository: for most, or later. A repository may have changed since.

Leaderboard · Armory