hubotio/hubot

A customizable life embetterment robot.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 10 minutes ago
Added to GitGenius on September 3rd, 2026
Created on August 27th, 2011
Open Issues & Pull Requests: 7 (+0)
GitHub issues: Enabled
Number of forks: 3,712
Total Stargazers: 16,797 (+0)
Total Subscribers: 579 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 28.4 hours
Mean response time: 157.3 days
90th percentile: 419.5 days
Tracked items: 34

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 14% of issues opened in the past year have been closed. Three people close 85% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 2,102 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • released (6)
  • enhancement (2)
  • documentation (1)
  • semantic-release (1)
  • triage: evolution (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Hubot is a framework for building chat bots that work across multiple chat services.

Hubot solves the problem of creating bots that can interact with teams across different chat platforms by providing a unified framework and library. The approach centers on extensibility through scripts that can be added to customize bot behavior. The framework includes a command bus subsystem that handles slash-style commands with built-in safety features, including optional confirmation requirements for commands that declare side effects. Commands support typed arguments with custom type resolvers, automatic help discovery, and permission controls based on both room membership and user roles.

Teams building bots for internal chat systems should consider Hubot if they need to support multiple chat adapters and want a script-based extension model. The framework suits projects where command-driven interactions are primary and where permission controls matter. The tool is particularly relevant for teams already using chat platforms as a central communication hub and wanting to automate workflows through bot commands.

The project maintains active test coverage across multiple operating systems. Development activity shows ongoing attention to the codebase with recent significant changes including a transition away from CoffeeScript toward modern JavaScript standards. The tool continues to receive updates addressing both core functionality and the JavaScript ecosystem's evolution.