Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI agent developers, robotics engineers, IoT developers, automation builders, AI-curious readers tracking the agent-perception space, engineering teams wiring AI agents to real-world sensors, and any developer wiring an AI agent to a standardized perception layer -- and who can pair machinepulse-ai/world2agent with the published npm scope `@world2agent` for the package surface, the webs
Who should use it
Who should skip it
Move on from machinepulse-ai/world2agent if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
machinepulse-ai/world2agent is tracked by RepoRadar as a apache-2.0 open protocol that st in the World2Agent (W2A): Open Perception Protocol for section. It was first seen on 2026-07-07 and last updated on 2026-07-07. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. The standout signals for machinepulse-ai/world2agent are workflow potential (9.4) and novelty (9.0), while maturity (5.8) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned machinepulse-ai/world2agent a composite score of 7.9 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The 1247* / 40-fork repo is at active maintenance but the protocol is new (push date 2026-05-09) and the sensor ecosystem is small -- the consumer SHOULD evaluate the sensor surface against the consumer's specific perception needs before adopting W2A; W2A is a perception protocol (sensors -> structured data); not an action protocol -- the consumer SHOULD plan for a separate action layer to do anything with the perceived data; the consumer SHOULD benchmark the standardized perception schema on 3+ sensor types before adopting.