detect-nodeinfo

Detect NodeInfo protocol endpoints and implementation patterns in codebases.

9|Updated Mar 12, 2026

Search Tags:#metadata #protocol detection #fediverse #activitypub #api endpoint #nodeinfo

Ready to run

npx skills add https://github.com/reiver/vibefed --skill detect-nodeinfo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: detect-nodeinfo
Source: https://github.com/reiver/vibefed/tree/main/skills/detect-nodeinfo
Command: npx skills add https://github.com/reiver/vibefed --skill detect-nodeinfo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify whether a codebase implements the NodeInfo protocol, a standard for exposing metadata about federated social network servers.

Core Features & Use Cases

Protocol Detection: Determines if a codebase has the /.well-known/nodeinfo discovery endpoint and/or a versioned schema endpoint.
Implementation Audit: Useful when auditing software for ActivityPub or other federated social networking support.
Use Case: You're reviewing a new social networking project and want to quickly confirm if it exposes instance metadata via NodeInfo, a common requirement for interoperability.

Quick Start

Use the detect-nodeinfo skill to check if the current codebase implements the NodeInfo protocol.

Frequently Asked Questions about detect-nodeinfo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check if a codebase implements the NodeInfo protocol endpoint?▼

To check for NodeInfo protocol implementation, scan the codebase for the `/.well-known/nodeinfo` discovery endpoint, versioned schema endpoints, and NodeInfo2 variants. This analysis identifies direct implementations, library delegations, and framework-specific patterns across multiple languages.

What is NodeInfo protocol detection used for in federated social networks?▼

NodeInfo protocol detection is used to determine if a federated social network server exposes instance metadata. It verifies the presence of the `/.well-known/nodeinfo` discovery endpoint, which is a common requirement for interoperability among ActivityPub and other federated platforms.

Can I audit a project for ActivityPub support by looking for NodeInfo endpoints?▼

Yes, you can audit a project for ActivityPub support by searching for NodeInfo endpoints. Detecting the `/.well-known/nodeinfo` route and its schema variants confirms that the codebase exposes the necessary metadata for federated social networking interoperability.

Does NodeInfo detection work across different programming languages and frameworks?▼

NodeInfo detection works across various programming languages and frameworks by analyzing code for direct implementations, library delegations, and framework-specific routing patterns. It identifies both standard discovery endpoints and NodeInfo2 variants regardless of the underlying stack.

How do I find NodeInfo2 variants in a codebase?▼

To find NodeInfo2 variants in a codebase, search for specific file paths and response patterns associated with the protocol. The detection process identifies both the standard `/.well-known/nodeinfo` discovery endpoint and alternative schema endpoints.

When do I need to detect NodeInfo endpoints in my codebase?▼

You need to detect NodeInfo endpoints when reviewing new social networking projects to confirm they expose instance metadata. This protocol detection is essential for auditing software for federated networking support and ensuring ActivityPub interoperability.