freshframework/fresh

The framework so simple, you already know it.

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

freshframework/fresh has 13k+ stars and 750+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 17, 2026. Data as of Oct 18, 08:54 UTC. Signed-in members get hourly updates — create a free account.

Summary Information

Updated 54 minutes ago

Type:FrameworkCategory(s):Full-Stack & Meta-Frameworks Backend Frameworks Web Development

Added to GitGenius on September 17th, 2022

Created on May 7th, 2021

Open Issues & Pull Requests: 159 (+0)

GitHub issues: Enabled

Number of forks: 758

Total Stargazers: 13,793 (+0)

Total Subscribers: 79 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 21.9 hours

Mean response time: 78.8 days

90th percentile: 265.6 days

Tracked items: 606

Most active contributors

Related repositories by overlapping contributors

Maintainer activity

2 people 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

Roughly one issue in four opened in the past year never receives a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "question" is answered fastest, typically in under an hour, while "bug" waits about 6 days. 80% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 57% of issues opened in the past year have been closed.

Issue Activity (beta)

Open issues: 83

New in 7 days: 2

Closed in 7 days: 1

Avg open age: 294 days

Stale 30+ days: 81

Stale 90+ days: 74

Recent activity

Opened in 7 days: 2

Closed in 7 days: 1

Comments in 7 days: 0

Events in 7 days: 1

Top labels

feat (62)
bug (50)
docs (27)
upstream (27)
question (19)
needs more info (18)
resolved-in-fresh-2 (14)
good first issue (9)

Most active issues this week

Explore full issue details

Detailed Description

Fresh is a next-generation web framework built on Deno and TypeScript that prioritizes speed, reliability, and simplicity. The framework is designed around the concept of island-based client hydration, which enables maximum interactivity while shipping zero JavaScript to the client by default. This architectural approach significantly reduces runtime overhead and improves initial page load performance. Fresh requires no configuration to get started, includes TypeScript support out of the box, and implements file-system routing similar to Next.js, making it accessible to developers already familiar with modern web frameworks.

The framework is built on Deno, a modern JavaScript runtime, and leverages Preact for component rendering. Fresh implements server-side rendering with an islands architecture, allowing developers to selectively hydrate interactive components while keeping the rest of the application static. This design pattern represents a shift away from traditional single-page application approaches that ship large amounts of JavaScript to browsers. The framework supports reactive templates and component-driven development, enabling developers to build full-stack applications with a unified TypeScript codebase.

Development workflow with Fresh centers around the Deno CLI and task runner. Developers can scaffold new projects using Fresh's initialization script, then use the deno task command to start a development server. The framework includes hot module reloading, allowing developers to see changes reflected in their browser immediately. Deployment is streamlined through Deno Deploy, which requires only pushing code to GitHub and creating a Deno Deploy project with no additional configuration needed.

This positioning reflects Fresh's role as a bridge between Deno's runtime environment and modern web development practices. The framework's classification spans multiple categories including modern web development, incremental rendering, reactive templates, and serverless deployment, highlighting its comprehensive approach to contemporary web application development. Fresh's documentation is hosted at usefresh.dev and includes detailed API references, getting started guides, and a showcase of projects built with the framework.