Tests As Behavioral Spec And Cloning Risk

Issue 56 Edition 2026-02-25 6 min read

General

Sources: 1 • Confidence: High • Updated: 2026-04-12 10:08

Key takeaways

A comprehensive public test suite can enable a fresh reimplementation of an open-source library from scratch, potentially in a different programming language.
tldraw filed a joke issue proposing translating its source code to Traditional Chinese as a purported defense against external AI coding agents replicating the project.
A tldraw maintainer argued that moving tests to another repository would complicate and slow development, and that development speed is a higher priority.
An issue suggesting tldraw would move its test suite to a private repository was later revealed to have been intended as a joke.
tldraw is described as not technically open source because its custom license requires a commercial license for production use.

A comprehensive public test suite can enable a fresh reimplementation of an open-source library from scratch, potentially in a different programming language.
The risk of test-driven reimplementation is described as particularly concerning for projects that pair open distribution with a commercial business model.
Cloudflare reportedly ported Next.js to use Vite in about a week using AI.

tldraw filed a joke issue proposing translating its source code to Traditional Chinese as a purported defense against external AI coding agents replicating the project.
tldraw is described as not technically open source because its custom license requires a commercial license for production use.
A tldraw maintainer suggested the project’s defensible value is in continually making strong product decisions for users rather than preventing others from recreating the code.

A tldraw maintainer argued that moving tests to another repository would complicate and slow development, and that development speed is a higher priority.

An issue suggesting tldraw would move its test suite to a private repository was later revealed to have been intended as a joke.

Are there documented cases where third parties produced close behavioral reimplementations primarily by leveraging a project’s public tests (with or without AI assistance)?
What were the exact scope, constraints, and artifacts behind the reported Cloudflare Next.js-to-Vite port (what was ported, what “about a week” includes, and how AI was used)?
What does the tldraw license actually require for production use, and how does it define “production” and “commercial license” obligations?
How common is it for commercially oriented OSS-like projects to consider restricting or relocating tests, and what concrete changes (if any) are being adopted outside this one example?
What is the measured development cost (build, CI, review, contributor experience) of splitting tests into a separate repository compared to keeping them co-located?

Public test suites may increase AI enabled reimplementation risk by acting as executable behavioral specifications, potentially weakening defensibility for commercially licensed OSS like projects where code access is broad.
Teams may prioritize development velocity over IP shielding even when replication risk is acknowledged, implying limited near term adoption of friction adding measures such as splitting or restricting tests.
Custom licensing that restricts production use can shift competitive moat emphasis from code secrecy to product decisions and execution, with AI replication concerns influencing messaging more than policy.

Documented third party cases of close behavioral reimplementations that explicitly credit public tests as the primary guide, including timelines and scope.
A detailed account of the reported rapid AI assisted port that specifies artifacts, effort included in the timeline, and how AI was used, showing feasibility of fast large scale reimplementation.
Concrete policy changes by commercially oriented OSS like projects to relocate, restrict, or gate test suites, along with measured impacts on build, CI, review speed, and contributor workflow.

Evidence that public tests rarely enable meaningful reimplementation without substantial source level access or domain knowledge, reducing the practical cloning pathway described.
Clarification that the project license terms and enforcement for production use materially limit economic impact from clones, reducing incentives to replicate behaviorally.
Repeated instances where attempts to restrict tests are reversed due to unacceptable velocity and tooling costs, indicating the approach is not operationally viable.