Trending repositories

Ranked by Attention Score: stars gained over the last 180 complete days

Period

Sort order

Tag

Filters (1)

Apply

Filters

Primary language

License

Total stars

Last push

Created

Archived

Clear all filters

9 repositories by Attention Score · May 8, 2026 – Nov 3, 2026 (UTC)

Language: Common Lisp
Tag: Backend and APIs
Clear all

1.fukamachi / woo

A fast non-blocking HTTP server on top of libev

common-lisp
webserver

Common Lisp MIT1.4K total101 forks

+40 stars

from 1,370 · score 3.71

2.fukamachi / dexador

A fast HTTP client for Common Lisp

common-lisp
http-client

Common Lisp No license438 total48 forks

+11 stars

from 427 · score 2.48

3.mmontone / djula

Common Lisp port of the Django templating language

template-engine
html-template
lisp
common-lisp

Common Lisp MIT169 total25 forks

+4 stars

from 165 · score 1.61

4.40ants / reblocks

A fork of Weblocks Common Lisp web framework

common-lisp
webframework

Common Lisp Other license102 total12 forks

+4 stars

from 98 · score 1.61

5.orthecreedence / wookie

Asynchronous HTTP server in common lisp

Common Lisp MIT197 total19 forks

+2 stars

from 195 · score 1.10

6.fukamachi / websocket-driver

WebSocket server/client implementation for Common Lisp

common-lisp
websocket

Common Lisp BSD-2-CLAUSE113 total29 forks

+2 stars

from 111 · score 1.10

7.joaotavora / hunchensocket

RFC6455 compliant WebSockets for Common Lisp

Common Lisp Other license121 total22 forks

+1 stars

from 120 · score 0.69

8.dnaeon / cl-jingle

Common Lisp web framework with bells and whistles (based on ningle)

common-lisp
lisp
web
webdev
webframework

Common Lisp Other license64 total8 forks

+1 stars

from 63 · score 0.69

9.40ants / openrpc

OpenRPC implementation for Common Lisp

api
common-lisp
json-rpc
open-rpc
rpc

Common Lisp No license34 total5 forks

+1 stars

from 33 · score 0.69

Order: Attention Score

Most net stars gained in the window first. The score only puts this gain on a log scale, so the order is the order of the gain.

How the ranking works

Ranked by stars gained in the window. The score is the natural log of one plus that gain, so a repository's rank is exactly its star gain's rank.

score = log1p(net stars gained in the trailing T complete UTC days)

A repository is ranked only when its Star History covers every day of the window and its latest Observation is not missing.

The longest window is 180 days. Star History from the Repository Host goes back at most 180 days before the first daily record that AwesomeRepos made for the repository. A longer window needs more of these daily records first. A repository younger than the window does not rank in it.

The filters select from the same eligible repositories. A repository matches the topics when it has any of them. Total stars is the count now. Last push and creation on the Repository Host count back from the start of today (UTC). The counts beside the languages, licenses, and topics include all ranked repositories in the window. A Tag holds the repositories that have it. See Tags.

Repositories enter the index from the starting dataset of the index, or by gaining stars faster than the published admission threshold, whatever their size. A repository stays in the index after it enters. Thus an archived repository can still rank.

Browse the Repository Index