Quavern Open source

What Quavern publishes.

The repositories Quavern opens, the licence they use, and the rules it follows when it opens code. Every repository lives at github.com/Quavern.

Repositories

Every public repository of the Quavern organisation, with the day it opened.

  1. oss.quavern.com

    Quavern/quavern.github.io

    The source of this site: a static build with no dependency, the Quavern Open Source License and this list.

    Publicsince QOSL-1.0

  2. Quavsit Observatory

    Quavern/quavsit-observatory

    A daily record of 147 French public-transport feeds as an engine reads them: when each timetable ends, how old each real-time feed is, and how much of its real-time data matches the timetable. In trial since 15 September 2026; measurements under CC BY 4.0.

    Publicsince QOSL-1.0

Licence

Quavern's repositories use the Quavern Open Source License, version 1.0 (QOSL-1.0). It is written to meet the Open Source Definition; it is not OSI-approved.

Quavern Open Source License 1.0

  • Use, study, change and share the code for any purpose.
  • A file of ours that you change stays under the licence when you distribute it or run it as a network service; the rest of your program stays yours.
  • Patents held by contributors are licensed with their code.
  • Credits to the producers of open data stay attached to the software.

The text of 15 September 2026 is a draft under legal review. This site's repository is its first use; if the review changes the text, the change gets a new version number.

How Quavern opens code

What stays closed
Code is opened where people need to inspect it, reuse it or trust it. Marl, Marl Code and the hosted Quavsit API stay closed: running them is the part customers pay for.
Open data keeps its licence
Open data keeps its licence and its credit: Licence Ouverte 2.0, ODbL, Licence Mobilités and the others named in each repository.
No secret in a repository
Provider keys, share links and personal details stay out of published code. A repository starts with its own history, never a copy of Quavern's private one.
Security reports stay private
Write to hello@quavern.com with "Security" in the subject, not in a public issue.
Contributions
Issues and pull requests are read. Each repository says what it accepts in its CONTRIBUTING file, and a contribution is received under the repository's licence.

Built on

Open-source software that Quavern's products depend on, with the licence each project publishes.

NetBSDThe base system of QuavernOS.BSD licences
FlaskThe APIs of Marl, myQuavern and Quavsit.BSD-3-Clause
NuxtThe Marl, myQuavern and Quavsit web applications.MIT
VueThe interface layer of those applications.MIT
GoThe language and toolchain of Marl Code.BSD-3-Clause
Bubble TeaThe terminal interface of Marl Code.MIT
SQLiteQuavsit's transit store and the platform database.Public domain
gtfs-realtime-bindingsReading GTFS-RT feeds in Quavsit.Apache-2.0
LinealThe display typeface of every Quavern surface.OFL-1.1
Atkinson Hyperlegible NextThe text typeface of every Quavern surface.OFL-1.1