Madeby

io.github.MadeByFYIPublished by GitHub account MadeByFYIv0.3.16Updated Nov 7, 2026

Disclose AI authorship of code per the ACO standard — tools for AI coding agents.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local CLI-backed server that records and checks AI-authorship disclosure in git commits, following the ACO provenance standard.

What you can do
  • Report authorship coverage for a repository, comparing disclosed and unknown authorship with a human/with-AI/AI mix
  • Set up the ACO AGENTS.md convention and a CI disclosure check in a repository
  • Check commits against a local disclosure policy file, advisory by default
  • Look up what is on the record for a file or the whole repository
  • Record that an AI agent authored HEAD, or affirm that a human authored it, optionally with AI assistance
When to use it
Useful when a team wants a verifiable record of which commits were AI-authored and a lightweight gate in CI, rather than trying to detect AI code after the fact.
Requirements
Runs as a local process over stdio via the npm package madeby; needs Node.js 22 or newer and a local git repository with commit history. No authentication, environment variables or headers are declared.
Before you install
It writes into the repository: init adds an AGENTS.md convention and a CI check, and the disclosure commands add trailers to commits. The policy check is advisory by default, so enforcement depends on configuration. It reports only what contributors declare and does not verify authorship itself.

Installation

In SourceWeft

  1. Open Madeby in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

MadeBy

Who made this thing? — a verifiable content-provenance layer, starting with code.

This is the v2 build. The design lives in the spec docs at the repo root:

  • ARCHITECTURE.md — asker-pull spine, hash-as-join-key, attestation standard, invariants
  • TESTING.md — the trust/QA doctrine (publishable conformance; verify without open source)

The first attempt is archived under archive/v1/ — reference only.

The CLI — madeby

The product ships as a zero-infra CLI that runs against your local git history. Disclosure, not detection: it reports what contributors put on the record and never guesses whether code is AI.

sh
npx madeby coverage   # the scoreboard: how much of your repo's authorship is disclosednpx madeby init       # drop the ACO AGENTS.md convention + a CI disclosure check into your reponpx madeby check      # the gate: do commits meet .madeby/policy.json? (advisory by default)npx madeby who        # made by whom? what's on the record for a file or the whole reponpx madeby ai         # an AI agent discloses it authored HEAD  (Authored-by-ai:)npx madeby me         # affirm you authored HEAD yourself (--with-ai [tool] for assisted)

madeby coverage is the maintainer's scoreboard — known (disclosed) vs unknown authorship, the human/with_ai/ai mix of the known, and the asserted-vs-verified trust split, as a labeled estimate. Built on ACO, the open Authorship Certificate of Origin standard. Full docs: packages/cli · on npm: madeby.

Repo layout

apps/web/            Next.js web app (Vercel)packages/core/       Shared deterministic trust logic — canonicalization,                       fingerprinting, tier resolution + conformance vectors.                       This is the publishable / open boundary (TESTING.md §4).workers/badge/       Cloudflare Worker — live-served badge SVGs        (stub)services/ingestion/  Python (Modal) — public-git ingestion + compute    (stub)

Develop

bash
pnpm installpnpm dev          # runs apps/web at http://localhost:3000pnpm typecheck    # tsc across packagespnpm build        # build all packagespnpm test         # trust-gate suite (conformance vectors land in #17)

Requires Node ≥ 22 and pnpm 10.

Provisioning (handoff)

The skeleton builds with no external services. To run against real infrastructure, copy .env.example → .env and fill in the values listed there.

Provenance (we dogfood)

This repo records its own provenance from commit zero — signed commits, Co-Authored-By: trailers, and a .madeby/ span manifest. See PROVENANCE.md; verify with pnpm provenance:verify-trailers.

Tickets

Work is tracked as GitHub issues, organized under epics (#1 dogfood, #4 foundations, #5 read-side, #6 producer-push, #16 trust-QA).

Source: README.md at commit a5c66c8

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

8
  1. v0.3.16LatestNov 7, 2026
  2. v0.3.12Oct 22, 2026
  3. v0.3.11Oct 20, 2026
  4. v0.3.10Oct 20, 2026
  5. v0.3.9Oct 20, 2026
  6. v0.3.7Oct 19, 2026
  7. v0.3.6Oct 16, 2026
  8. v0.3.4Oct 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.