ktbyers/netmiko

Multi-vendor library to simplify Paramiko SSH connections to network devices

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 11 seconds ago
Added to GitGenius on September 16th, 2026
Created on November 28th, 2014
Open Issues & Pull Requests: 63 (+0)
GitHub issues: Enabled
Number of forks: 1,388
Total Stargazers: 4,287 (+0)
Total Subscribers: 196 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.1 hours
Mean response time: 130.4 days
90th percentile: 556.0 days
Tracked items: 246

Most active contributors

Sign in to see contributor activity.

How this project is maintained

82% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 7 hours, while "enhancement" waits about 2 weeks. Three people close 88% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 39
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 718 days
Stale 30+ days: 35
Stale 90+ days: 33

Recent activity

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

Top labels

  • bug (24)
  • enhancement (22)
  • f5 (3)
  • documentation (2)
  • New Platform (1)
  • priority (1)

Detailed Description

Netmiko is a Python library that simplifies SSH connections to network devices across multiple vendors.

The library addresses the complexity of managing SSH sessions to diverse network equipment by wrapping Paramiko with vendor-specific handlers. Rather than writing custom SSH logic for each device type, developers use a unified interface that abstracts away the differences between vendors. The tool handles device-specific quirks like command prompts, authentication flows, and output parsing, allowing users to send commands and retrieve results through simple method calls without managing low-level SSH details.

Netmiko suits teams managing heterogeneous network infrastructure who need programmatic access to devices for automation, configuration, or monitoring tasks. It works well for network engineers building operational scripts or larger automation frameworks that must interact with equipment from multiple manufacturers. The library is particularly valuable when you need consistent behavior across vendor boundaries without writing vendor-specific connection logic.

The project shows sustained development activity with regular updates addressing bug fixes and new device support. Contributions flow in steadily, indicating ongoing community engagement with the codebase. The maintainer remains actively involved in reviewing and merging changes, keeping the project responsive to reported issues and feature requests.