marko-js/marko

A declarative, HTML-based language that makes building web apps fun

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 6 minutes ago
Added to GitGenius on September 4th, 2026
Created on January 7th, 2014
Open Issues & Pull Requests: 31 (+0)
GitHub issues: Enabled
Number of forks: 662
Total Stargazers: 14,409 (+0)
Total Subscribers: 194 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 659 days
Stale 30+ days: 6
Stale 90+ days: 3

Recent activity

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

Top labels

  • type:unverified bug (52)
  • type:feature (18)
  • type:docs (6)
  • status:backlog (4)
  • proposal (3)
  • status:todo (3)
  • type:bug (3)
  • type:question (3)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Marko is a declarative, HTML-based language for building web applications with client-side and server-side rendering capabilities.

Marko addresses the challenge of building dynamic user interfaces by extending HTML with modern programming constructs while keeping the syntax familiar to web developers. The language treats almost any valid HTML as valid Marko and adds features like custom components, conditionals, loops, and a built-in reactivity system. This approach allows developers to write interactive applications using an HTML-like syntax rather than learning a separate templating or component language.

Marko suits teams building isomorphic applications that need to render on both server and client, or projects where developers prefer HTML-based syntax over JavaScript-centric frameworks. It works well for building reusable UI components with reactive state management. The tool is particularly valuable for developers who want to stay close to HTML semantics while gaining modern application-building features, and for teams already invested in Node.js ecosystems.

The project shows measured development activity with a typical response to issues or pull requests arriving within one to two weeks. Work in the issue tracker centers on unverified bugs, feature requests, and documentation improvements, indicating a focus on stability, capability expansion, and keeping guidance current.