{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_filipljoljic-component-analyzer","slug":"filipljoljic-component-analyzer","name":"component-analyzer","type":"repo","url":"https://github.com/filipljoljic/component-analyzer","page_url":"https://unfragile.ai/filipljoljic-component-analyzer","categories":["data-analysis"],"tags":["mcp","model-context-protocol","smithery:filipljoljic/component-analyzer"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_filipljoljic-component-analyzer__cap_0","uri":"capability://data.processing.analysis.component.relationship.mapping","name":"component relationship mapping","description":"This capability analyzes the React component tree by traversing the codebase and extracting component relationships, props, and hooks used within each component. It employs a static analysis approach to build a visual representation of how components interact, allowing developers to see dependencies and hierarchies clearly. This distinct mapping helps in identifying complex components and their connections, which is crucial for effective refactoring.","intents":["How can I visualize the relationships between my React components?","What are the dependencies of a specific component in my codebase?","Can I get an overview of my component architecture?"],"best_for":["frontend developers managing large React applications"],"limitations":["Static analysis may miss dynamic component relationships established at runtime","Limited to React components only"],"requires":["Node.js 14+","React project structure"],"input_types":["code"],"output_types":["structured data","visual diagrams"],"categories":["data-processing-analysis","react-development"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_filipljoljic-component-analyzer__cap_1","uri":"capability://data.processing.analysis.refactor.hotspot.identification","name":"refactor hotspot identification","description":"This capability scans the codebase to identify components that are overly complex or have high coupling with other components, marking them as refactor hotspots. It leverages metrics such as cyclomatic complexity and component size to prioritize which components require immediate attention. This systematic approach helps teams focus their refactoring efforts where they will have the most impact.","intents":["Which components in my application need refactoring?","How can I prioritize refactoring tasks based on complexity?","What are the most problematic areas in my React code?"],"best_for":["teams looking to improve code maintainability in React projects"],"limitations":["May not account for all contextual factors influencing complexity","Relies on static metrics that might not reflect runtime behavior"],"requires":["Node.js 14+","React project structure"],"input_types":["code"],"output_types":["structured data","report"],"categories":["data-processing-analysis","code-quality"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_filipljoljic-component-analyzer__cap_2","uri":"capability://data.processing.analysis.props.and.hooks.inspection","name":"props and hooks inspection","description":"This capability inspects the props and hooks used in each component by parsing the component definitions and extracting relevant information. It provides a detailed overview of how data flows through components and which hooks are utilized, enabling developers to understand the functional aspects of their components better. This is achieved through a combination of AST parsing and static analysis techniques.","intents":["How can I see what props a component is using?","What hooks are being utilized in my components?","Can I get a detailed report of component props and hooks?"],"best_for":["developers needing to audit component usage in React applications"],"limitations":["Static analysis may not capture props passed dynamically or through context providers","Limited to React components only"],"requires":["Node.js 14+","React project structure"],"input_types":["code"],"output_types":["structured data","report"],"categories":["data-processing-analysis","react-development"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_filipljoljic-component-analyzer__cap_3","uri":"capability://data.processing.analysis.component.complexity.analysis","name":"component complexity analysis","description":"This capability evaluates the complexity of each React component based on various metrics such as lines of code, number of props, and dependencies. It generates a complexity score that helps developers assess which components might be difficult to maintain or understand. By using a combination of static code analysis and metric calculations, it provides a quantitative approach to component evaluation.","intents":["How complex is my component structure?","Can I get a complexity score for my components?","What components are likely to be hard to maintain?"],"best_for":["teams aiming to improve code maintainability and readability"],"limitations":["Complexity scores are subjective and may not reflect actual maintainability","Static analysis may not account for runtime behavior"],"requires":["Node.js 14+","React project structure"],"input_types":["code"],"output_types":["structured data","report"],"categories":["data-processing-analysis","code-quality"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":26,"verified":false,"data_access_risk":"low","permissions":["Node.js 14+","React project structure"],"failure_modes":["Static analysis may miss dynamic component relationships established at runtime","Limited to React components only","May not account for all contextual factors influencing complexity","Relies on static metrics that might not reflect runtime behavior","Static analysis may not capture props passed dynamically or through context providers","Complexity scores are subjective and may not reflect actual maintainability","Static analysis may not account for runtime behavior","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.33,"ecosystem":0.48999999999999994,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.3,"quality":0.2,"ecosystem":0.15,"match_graph":0.3,"freshness":0.05}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:26.346Z","last_scraped_at":"2026-05-03T15:19:09.933Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=filipljoljic-component-analyzer","compare_url":"https://unfragile.ai/compare?artifact=filipljoljic-component-analyzer"}},"signature":"WQb32J3ucEzMVspT/MNnTrdU9hYUMcbwSMeEr/7iUlU8FGB1mNyCJDwy5ZCW2egQgsWPGkoGkx56UH2xg7KtCw==","signedAt":"2026-06-21T15:05:55.232Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/filipljoljic-component-analyzer","artifact":"https://unfragile.ai/filipljoljic-component-analyzer","verify":"https://unfragile.ai/api/v1/verify?slug=filipljoljic-component-analyzer","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}