Search for 'the'

For details on the search query syntax, see the guide.

Total results: 3174, showing 601 - 624

Note: artifacts in italics are non-canonical forks. See the wiki for more details.


  • The Burning Swell RabbitMQ client library
  • oss-jdbc 0.8.0

    OSS-JDBC is an empty Maven project that depends on several Open Source JDBC drivers. The sole purpose of this project is to automatically pull in JDBC driver JARs as Maven dependencies, each of which may have its own license.

  • Common parts of the project

  • Drake: the data processing workflow tool (a.k.a. 'make for data')

  • clojars fork of pinyin4j, until we can get the real thing in a maven repo
  • clj-obt 0.5.1

    Library for accessing the Oslo-Bergen-Tagger, and parsing of the output.

  • List the license of each of your dependencies.

  • When running the repl, reload every time a file is saved.

  • Logging library for the Duct framework
  • monome-serial 0.4-SNAPSHOT

    A library for the monome (http://monome.org). Implements the overtone.device.grid protocol.

  • A babashka compatible library for accessing the gitlab API

  • A helper library for writing models in the style of Witan workspaces.

  • Clojure implementation of the Model Context Protocol (MCP)

  • The latest Telegram Bot API specification and client lib for Clojure-based apps.

  • The Burning Swell Transit format library.
  • reverie-sql 0.9.0-SNAPSHOT

    The SQL backbone of reverie; a CMS for power users

  • Avoid the Jungle

  • Displays all comment annotations in the project.

  • A Duct library for interacting with the Stripe API

  • The PagerDuty API provides programmatic access to entities within a PagerDuty account. It is designed around [RESTful principles](https://en.wikipedia.org/wiki/Representational_state_transfer) with a path structure based on resources and their relationships. All requests and responses are serialized in [JSON](https://en.wikipedia.org/wiki/JSON), including error responses. Schema are designed to be reusable across requests and across endpoints. More sophisticated API clients should treat PagerDuty resources as unique objects keyed by the `id` field that can be used in any API request involving resources of that type. Every resource contains a `type` field that identifies the schema it uses. ## Rate limiting Each account and authentication mechanism is limited to the number of API requests it can make every minute. API requests that exceed the API rate limit will return an [HTTP status code](error_codes.html#http_responses) of 429. Different requests may affect your rate limit differently, so clients should always be prepared to be rate limited and respond appropriately. ## Read-Only API Keys API requests made with read-only keys attempting to access endpoints with methods other than `GET` will return an [HTTP status code](error_codes.html#http_responses) of 403. ## Error Codes Most APIs will return an error code from an unsuccessful call. They are described [here](error_codes.html).

  • Healthcheck component for the reloadable pattern.

  • A Clojure library for generation and utilization of UUIDs (Universally Unique Identifiers) as described by RFC-4122. This library extends the standard Java UUID class to provide true v1 (time based) and v3/v5 (namespace based) identifier generation. Additionally, a number of useful supporting utilities are provided to support serialization and manipulation of these UUIDs in a simple, efficient manner.

  • rpc based on the redis protocol

  • This repo contains the code for the ui components for the offcourse platform