EngineeringOne repository for everything we build.

Every NoirSystems product, website, library and tool lives in one monorepo: one clone, one toolchain, one CI. This page is that repository, measured.

See the projectsWork with us

The repository
in numbers

Counted in the repository on October 17, 2026. Lines are non-blank lines of source code, without lockfiles, build output, vendored or generated code.

0

projects

0

programming languages

0

commits

0

files

0+

lines of code

The repository
as a city

Every project is a building: its height is its lines of code, its colour the language most of it is written in. The five directories are its districts.

Point at a building to see what it is.

Every project, by lines of code
ProjectDirectoryMain languageLines of code
flokzyproducts/TypeScript181,690
crypto-ideproducts/TypeScript127,421
drukkoproducts/TypeScript105,721
lavenderproducts/TypeScript75,004
kvbnewsproducts/Go56,121
pikajuoksuproducts/TypeScript51,922
noir-botsproducts/Python32,057
sunflowproducts/Go29,906
A product not announced yetproducts/19,799
pikajuoksu-corelibs/TypeScript17,347
noirid-siteweb/TypeScript15,517
levonneproducts/Go15,196
noirsystems-siteweb/TypeScript13,939
foldtoolsproducts/Kotlin11,041
A product not announced yetproducts/10,225
pikajuoksu-serverproducts/TypeScript10,052
noirwalletproducts/TypeScript9,393
etatproducts/Java8,970
A product not announced yetproducts/8,262
xandra-csslibs/JavaScript6,144
noir-designlibs/CSS4,274
noir-bzhweb/TypeScript4,210
A product not announced yetproducts/4,049
noir-appproducts/TypeScript3,380
bookdiscordproducts/JavaScript2,830
flokzywebproducts/TypeScript1,906
redstone-siteweb/TypeScript1,512
gitytools/JavaScript1,175
A product not announced yetproducts/401
migrationtools/Shell358
gitcomtools/Shell173
gopolarsresearch/0

Commits,
almost every day

Since Dec 11, 2025, 11 people have committed to NoirSystems. The darkest squares are days counted in the monorepo’s own history.

  • 0people committing
  • Dec 11, 2025first commit
  • 0commits in the monorepo

Point at a square to see its day.

32 projects,
five directories

Each directory means one thing, and a project lives in the one that says what it is.

 

  • flokzy

    products/flokzy

    • TypeScript
    • Kotlin

  • sunflow

    products/sunflow

    • Go
    • TypeScript

  • crypto-ide

    products/crypto-ide

    • TypeScript

  • lavender

    products/lavender

    • Rust
    • TypeScript

  • kvbnews

    products/kvbnews

    • Go
    • TypeScript
    • Python

  • drukko

    products/drukko

    • TypeScript

  • noir-app

    products/noir-app

    • TypeScript

  • noirwallet

    products/noirwallet

    • TypeScript

  • pikajuoksu

    products/pikajuoksu

    • TypeScript

  • pikajuoksu-server

    products/pikajuoksu-server

    • TypeScript

  • levonne

    products/levonne

    • Go
    • Dart

  • foldtools

    products/foldtools

    • Kotlin
    • Swift

  • noir-bots

    products/noir-bots

    • Python

  • flokzyweb

    products/flokzyweb

    • TypeScript

  • etat

    products/etat

    • Java
    • Python

  • bookdiscord

    products/bookdiscord

    • JavaScript

  • noirsystems-site

    web/noirsystems-site

    • TypeScript

  • noir-bzh

    web/noir-bzh

    • TypeScript

  • noirid-site

    web/noirid-site

    • TypeScript

  • redstone-site

    web/redstone-site

    • TypeScript

  • noir-design

    libs/noir-design

    • CSS
    • TypeScript

  • xandra-css

    libs/xandra-css

    • CSS
    • JavaScript

  • pikajuoksu-core

    libs/pikajuoksu-core

    • TypeScript

  • gitcom

    tools/gitcom

    • Python

  • gity

    tools/gity

    • JavaScript

  • migration

    tools/migration

    • Shell
    • Python

  • gopolars

    research/gopolars

    • Go

  • +5

    internal projects, not listed here

What it is
written in

Lines of code by language, across the whole repository.

Lines of code by language, across the whole repository.
LanguageLines of code
TypeScript
512,977
Kotlin
77,971
Go
58,392
Rust
37,237
JavaScript
37,031
Python
36,307
CSS
33,443
Java
12,699
Shell
11,226
Other
12,712, SQL, Dart, Swift

No productdepends on another

Nx sees one shared library, the NoirSystems design system, used by the three websites, and no dependencies between products. That is the measured state, and we keep it that way: no product imports code from another product.

Leave the graph disconnected. Do not manufacture edges to make it look like a monorepo.

ADR-0002, accepted on 20 September 2026

The one real link is a protocol

CodeSea talks to Flokzy over HTTP, with a versioned protocol, a test fixture and a delivery outbox. Two programs talking over the network are not an import, so the graph is right not to draw it.

What one repository buys

  • One clone
  • One toolchain setup
  • One CI
  • One place to search

Four rules
that hold it together

  • No product imports another

    A product may use libs/ and its own code. Products talk to each other through an API, an event contract or a generated client.

  • libs/ is earned

    Code moves into libs/ when a second product, in a different area, already uses it. There is no shared dumping ground.

  • Every project owns its install

    Each project keeps its own package manager and lockfile. The root installs Nx and nothing else.

  • Secrets stay out

    Environment files, keys and keystores are ignored by git, and every push scans the whole history for leaks.

Seven commands
for every project

Task names are the same in every project, whatever runs underneath: Gradle, Go, pnpm, Maven or pytest.

The same targets everywhere

  • build
  • test
  • lint
  • typecheck
  • format
  • dev
  • e2e
  • integration-test
  • package
  • deploy
  • pnpm bootstrap# toolchains, install, git hooks, health check
  • pnpm env:check# what is wrong with this machine, and the fix
  • pnpm projects# what exists
  • pnpm graph# how it fits together
  • pnpm affected# lint, typecheck, test and build, only what changed
  • pnpm check# dependency boundaries and the structure contract
  • npx nx run <project>:<target># one project, one task

Every push,
one pipeline

CI runs the same scripts you run on your machine, and only for the projects the change touched.

  1. Secret scan

    gitleaks scans the full history, after a control test proves it catches a planted key.

    gitleaks git .

  2. Toolchains

    mise installs the exact versions pinned in mise.toml.

    mise install

  3. Boundaries

    pnpm check first plants a known bad dependency, so a clean result means the rules really ran.

    pnpm check

  4. Affected

    Nx works out which projects the change touches.

    nx show projects --affected

  5. Install

    Only the affected projects install their dependencies.

    pnpm install:affected

  6. Verify

    Lint, typecheck, test and build, three projects at a time.

    pnpm affected --parallel=3

Want to workin it?

No open roles are listed right now, but open applications are read. Tell us which product you want to work on.

See Jobshello@noirsystems.com