m1k1o/neko

A self hosted virtual browser that runs in docker and uses WebRTC.

View on GitHub ↗Jump to charts ↓Open shareable report →

m1k1o/neko has 22k+ stars and 1.5k+ forks on GitHub, is written in Go, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 32 minutes ago
Added to GitGenius on July 28th, 2025
Created on March 14th, 2020
Open Issues & Pull Requests: 147 (+0)
GitHub issues: Enabled
Number of forks: 1,638
Total Stargazers: 22,514 (+0)
Total Subscribers: 103 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.3 hours
Mean response time: 113.6 days
90th percentile: 437.2 days
Tracked items: 245

Maintainer activity

1 person did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 9% of issues opened in the past year have never received a reply. 93% 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 3 hours, while "not our bug" waits about 7 days. 76% of issues opened in the past year have been closed, leaving a working backlog. Three people close 81% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 93
New in 7 days: 2
Closed in 7 days: 3
Avg open age: 537 days
Stale 30+ days: 88
Stale 90+ days: 75

Recent activity

Opened in 7 days: 2
Closed in 7 days: 3
Comments in 7 days: 4
Events in 7 days: 9

Top labels

  • enhancement (47)
  • question (32)
  • documentation (27)
  • discussion (22)
  • bug (19)
  • not our bug (14)
  • help wanted (8)
  • good first issue (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Neko is a lightweight, fast, and extensible static site generator (SSG) written in Go. It aims to provide a simple yet powerful alternative to more complex SSG options like Hugo or Jekyll, focusing on speed and ease of configuration. The core philosophy revolves around using data files (YAML, JSON, TOML) to drive content generation, combined with Go templates for rendering. It's particularly well-suited for blogs, documentation sites, and simple websites where performance is a priority.

The repository's structure is relatively straightforward. The `cmd/neko` directory contains the main application logic for building the site. `internal` houses the core functionalities like template parsing, data loading, and file system operations. `pkg` contains reusable components that could potentially be used in other projects. Crucially, Neko doesn't enforce a rigid directory structure for content; it's designed to be flexible, allowing users to organize their content in a way that makes sense for their project. This is achieved through configuration files that define data sources and template mappings.

A key feature of Neko is its data-driven approach. Content isn't directly embedded within templates. Instead, data is loaded from files (YAML, JSON, TOML are supported out-of-the-box, with potential for extension) and then passed to the templates for rendering. This separation of content and presentation makes it easier to manage and update content without modifying the templates themselves. The configuration file specifies where to find these data files and how they should be processed. Neko also supports front matter within Markdown files, allowing for metadata to be associated with each piece of content.

Templating is handled using Go's built-in `html/template` package, providing a familiar and powerful templating engine. This allows for complex logic and dynamic content generation within the templates. Neko provides helper functions within the template context to simplify common tasks like URL generation, date formatting, and content filtering. The templates themselves are organized in a directory specified in the configuration file, and Neko recursively searches this directory for `.html` files.

Extensibility is another important aspect of Neko. While it provides a solid foundation out of the box, it's designed to be easily extended through custom functions and shortcodes. Users can define their own Go functions and make them available within the template context, allowing for highly customized content generation. Shortcodes, which are reusable snippets of HTML or template code, can also be defined to simplify the creation of common elements. The project is actively maintained and welcomes contributions, suggesting a growing community and ongoing development. Overall, Neko offers a compelling option for developers seeking a fast, flexible, and easy-to-use static site generator.