Gitit

A wiki written in Haskell that stores pages in Git, Darcs or Mercurial and renders Markdown and other formats through pandoc.

2.3k stars, 233 forks Haskell On GitHub since November 2008

View on GitHub How to run it

Gitit at a glance

Open sourceYes, GPL-2.0No paid parts in the repository
Health44 of 100Actively developed
Self-hostingFrom sourceSteps in the README
InterfaceEnglish onlyNo translation files found
Issue repliesWithin ~8 hoursMedian first reply; 60% of recent issues answered

What is Gitit?

Gitit keeps every page and uploaded file in a version control repository, so you can edit through the web interface or with ordinary Git, Darcs or Mercurial commands. Pandoc processes the markup: extended Markdown by default, or reStructuredText, LaTeX, HTML, DocBook and Org-mode. It can show TeX math and highlighted source code, supports categories, caching and Atom feeds, and accepts plugins written in Haskell. It is built from source with the stack tool.

Good fit if

  • You want a wiki whose history lives in a Git repository you can clone and grep.
  • You write technical notes with math and code and like pandoc's formats.

Look elsewhere if

  • You want a polished team wiki with editors and permissions: BookStack or Wiki.js.
  • You want personal Markdown notes on your desktop: Zettlr.

Before you adopt it

Gitit is GPL-2.0 and has no paid parts. It dates from 2008 and is maintained mostly by one person, its original author, with occasional commits and no formal releases. You need a Haskell toolchain to build it, as there is no Docker setup.

Drafted with AI from the project's README and repository data, then checked against that data on 31 October 2026. Report a correction

How to run Gitit yourself

Docker
No Docker files in the repository
Compose file
None in the repository
Setup effort
Not rated: no compose file to judge from
Kubernetes
No Helm chart in the repository
Desktop and mobile
No app builds in GitHub releases
Interface languages
English only

Install instructions: the README on GitHub.

Gitit health: is it still maintained?

44 of 100, actively developed

Release rhythmNo releasesNone published on GitHub
Issue repliesWithin ~8 hoursMedian first reply; 60% of recent issues answered
Bus factorHigh riskThe most active of 2 authors wrote 83% of recent commits
  • Activity
    12 commits in the last 90 days, the latest on 25 October 2026.
    13 / 30
  • Contributors
    2 people wrote the 12 commits of the last 90 days; the most active wrote 83% of them.
    4 / 20
  • Releases
    No releases published on GitHub.
    6 / 20
  • Replies to issues
    Maintainers answered 60% of recent issues, with a median first reply after 8 hours.
    17 / 20
  • Security practices
    OpenSSF Scorecard 3.9 of 10.
    4 / 10

Read from GitHub on 6 November 2026. How the score works

Gitit security practices

OpenSSF Scorecard checks how a project is developed and released: reviews, protected branches, pinned dependencies, signed releases. It does not audit the code itself.

OpenSSF Scorecard3.9 of 10How the project is built and released
Security policyNoNo SECURITY.md or similar

What each check found

  • Binary files10 / 10No compiled binaries checked into the repository
  • Dangerous workflows10 / 10No risky patterns in GitHub Actions
  • License file10 / 10A license file is present
  • Maintained10 / 10Steady commits and issue activity in the last 90 days
  • Code review1 / 10Some changes are merged without review
  • Best-practices badge0 / 10No OpenSSF Best Practices badge
  • Branch protection0 / 10The main branch has no protection rules
  • Fuzzing0 / 10No fuzz testing found
  • Pinned dependencies0 / 10Dependencies are not pinned to fixed versions
  • Security policy0 / 10No security policy
  • Static analysis0 / 10No static analysis found
  • Token permissions0 / 10CI tokens have broad write rights

From the OpenSSF Scorecard of 26 October 2026. Checks that do not apply to Gitit are left out.

Gitit license: is it open source?

Gitit uses GPL-2.0, an open-source license approved by the OSI.

  1. November 2008First published on GitHub.
  2. TodayGPL-2.0.

Gitit for developers

Written in

  • Haskell 68%
  • JavaScript 25%
  • CSS 5%
  • StringTemplate 1%
  • Shell <1%
  • Other <1%

Getting involved

Contributing guideNot foundNo CONTRIBUTING file in the repository
Open issues189On GitHub
Authors, 90 days2Of 12 commits
DonationsGitHub SponsorsListed on GitHub

Language shares are GitHub’s count of the code in the repository.

Alternatives to Gitit

  • DocmostDocmost is an open-source collaborative wiki and documentation software. It is an open-source alternative to… 73 health · AGPL-3.0 · 22.2k stars
  • DokuWikiThe DokuWiki Open Source Wiki Engine 69 health · GPL-2.0 · 4.7k stars
  • Wiki.jsWiki.js | Next Generation Open Source Wiki 65 health · AGPL-3.0 · 29.2k stars
  • TiddlyWikiA self-contained JavaScript wiki for the browser, Node.js, AWS Lambda etc. 65 health · BSD · 8.7k stars
  • MemosMemos is an open-source, self-hosted note-taking app that brings your everyday thoughts together in a… 86 health · MIT · 64.3k stars

All 36 projects in Notes & knowledge bases

Questions about Gitit

Is Gitit open source?

Yes. Gitit is published under GPL-2.0, an OSI-approved open-source license.

Is Gitit still maintained?

Its health score is 44 of 100 (actively developed). It had 12 commits in the last 90 days, the latest on 25 October 2026.

How do I run Gitit?

The repository has no Docker files or app builds, so you build it from source. The README on GitHub has the steps.

What is Gitit written in?

Gitit is written mainly in Haskell (68% of the code), with JavaScript (25%) and CSS (5%), by GitHub’s count of the repository.

What are the alternatives to Gitit?

Close alternatives in the Notes & knowledge bases category include Docmost, DokuWiki, Wiki.js.