Developer guide
Protect your source code, the developer's guide
Your code is protected by copyright from the moment you write it. The problem is not protection, it is proof. A git history can be forged with one command, a GitHub repo can be deleted. Here is how to establish solid prior existence.
What the law says
In Europe as in the United States, source code is protected by copyright as a literary work. This protection is automatic upon writing, without formality, in the 181 countries of the Berne Convention.
Mind the limits. Copyright protects expression, your code as written, not ideas, algorithms or features. A competitor can reimplement your idea. They cannot copy your code.
In case of copying, everything comes down to one point, proving your version existed before theirs. That is proof of prior existence.
What does NOT prove prior existence
Git history
Commit dates are declarative. An environment variable (GIT_COMMITTER_DATE) is enough to backdate a commit. A git history alone is inadmissible as proof of date.
A GitHub repo
GitHub is a private platform. A repo can be deleted, rewritten (force push) or made private. GitHub certifies no date and will not testify for you.
The license (MIT, GPL...)
A license organizes how others may use your code. It presupposes you are the author, it does not prove it. In a dispute, a license is useless without proof of prior existence.
Proof methods compared
| Method | Cost | Evidential value | Fits a dev workflow |
|---|---|---|---|
| Git history alone | β¬0 | Nearly none (dates can be forged) | Yes, but useless in a dispute |
| APP deposit (French software protection agency) | Several hundred euros + membership | Strong, historical reference for software in France | No, heavy procedure per version |
| Bailiff report | β¬200 to β¬500 per report | Very strong | No, unthinkable at every release |
| Copyright01 timestamped deposit | β¬0 (3 deposits), then from β¬4.90 | SHA-256 fingerprint + timestamp, publicly verifiable | Yes, deposit a repo in 2 minutes, API available |
Indicative prices observed in 2026.
How to deposit your code
Two methods depending on your workflow.
Deposit a GitHub repo
Paste the repo URL. Copyright01 automatically extracts metadata (commits, contributors, languages) and can commit a certification badge to your README.
Deposit a ZIP archive
For private or non-GitHub code, deposit an archive of your project. The file is AES-256 encrypted, nobody but you can access it.
Prefer automation? A REST API lets you deposit at every release, from your CI or a script. API documentation β
What about code updates?
Software evolves. Best practice is to deposit meaningful versions, the first public version, then major releases. Each deposit establishes the prior existence of the code state at its date.
No need to deposit every commit. In a dispute, what matters is proving that the copied part existed on your side first. Deposits at each major version are largely sufficient.
Frequently asked questions
Can open source code be protected?
Yes. Open source does not mean authorless. The license (MIT, GPL...) defines usage conditions, but you remain the copyright holder. A timestamped deposit proves your authorship if someone appropriates your work or violates the license.
What exactly should I deposit, the whole repo?
Deposit the complete project archive or the GitHub repo. The SHA-256 fingerprint covers all deposited content. Exclude dependencies (node_modules, vendor), they are not your work.
Does a deposit protect my algorithm?
No. Copyright protects written code, not the algorithm as an idea. For an algorithm, possible protections are trade secret or, in some countries, patents. The deposit proves the prior existence of your implementation.
Can AI-assisted code be protected?
The topic evolves by jurisdiction. What stays constant is that your human creative contribution (architecture, choices, assembly, fixes) remains protectable. A timestamped deposit fixes the state of your work at a date, whatever the share of assistance.
Deposit your first repo for free
3 free deposits, automatic GitHub extraction, README badge.
Protect my code