Discovery of source code in litigation

Introduction

Discovery of source code in litigation refers to the legal process through which a party seeks access to computer program instructions held by another party for examination and use as evidence in judicial proceedings. Source code is the human-readable form of software written in programming languages. It explains how a programme performs particular functions, processes information, communicates with other systems and generates outputs.

Discovery may become important in disputes involving software copyright infringement, patent violations, contractual obligations, cybersecurity incidents, algorithmic discrimination and technological defects. Unlike ordinary documents, source code may contain valuable trade secrets, proprietary methods and security-sensitive information. Therefore, courts must balance the need for relevant evidence with intellectual property protection and commercial confidentiality.

Legal framework in India

1. Code of Civil Procedure, 1908

The Code of Civil Procedure provides the principal procedural framework for discovery and inspection in civil litigation. Order XI permits parties to seek disclosure and production of relevant documents and electronic records. Where source code is directly connected with disputed software functionality or alleged infringement, a court may consider ordering its production or inspection.

The requesting party must demonstrate relevance and explain why ordinary documentation, software demonstrations or expert reports would not sufficiently establish the disputed facts. Courts can impose conditions to prevent unnecessary disclosure.

2. Commercial Courts Act, 2015

The Commercial Courts Act introduced a more structured disclosure and discovery framework for commercial disputes. Order XI of the Code of Civil Procedure, as substituted for commercial disputes, requires detailed disclosure of relevant documents and provides mechanisms for production and inspection.

Software licensing, intellectual property and technology-related contractual disputes may fall within commercial jurisdiction when they satisfy the statutory requirements. Source code may consequently become part of the documentary discovery process where it is material to the controversy.

3. Copyright Act, 1957

Section 2(o) of the Copyright Act recognises computer programmes as literary works. Sections 13 and 14 establish copyright protection and exclusive rights in qualifying software. Section 51 deals with infringement.

In software copyright litigation, discovery of source code may help determine whether protected program elements have been copied or reproduced. However, discovery should distinguish protectable expression from general functionality, ideas and programming methods.

4. Bharatiya Sakshya Adhiniyam, 2023

The Bharatiya Sakshya Adhiniyam, effective from 1 July 2024, governs electronic and digital evidence. Source code, technical logs, digital files and software-generated records may be relevant evidence depending on the issues involved. Their authenticity and integrity must be established under the applicable evidentiary rules.

Important case laws

1. Autodesk Inc. v. A.V.T. Shankardass (2008) 37 PTC 36 (Del)

This software copyright dispute concerned alleged unauthorised use of computer programmes. It illustrates the importance of establishing software ownership, licensing rights and unauthorised use through technical and documentary evidence. Although it is not a direct ruling establishing a general source code discovery right, its subject matter demonstrates why access to relevant software material may become important in infringement proceedings.

2. Microsoft Corporation v. Yogesh Papat (2005) 30 PTC 245 (Del)

The Delhi High Court dealt with unauthorised use of Microsoft software and the protection of computer programmes under copyright law. The dispute highlights the significance of software licensing and evidence concerning unauthorised reproduction or use. In comparable litigation, source code examination may assist in determining whether protected software expression has been copied.

3. Anvar P.V. v. P.K. Basheer (2014) 10 SCC 473

The Supreme Court explained the requirements for admitting electronic records under Section 65B of the former Indian Evidence Act, 1872. The decision is relevant where source code files, computer-generated reports or other electronic material are produced during litigation. Its evidentiary principles must now be considered alongside the Bharatiya Sakshya Adhiniyam, 2023.

4. Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal (2020) 7 SCC 1

The Supreme Court reaffirmed the importance of statutory certification for certain electronic records under the former Section 65B framework. The judgment assists courts in evaluating the admissibility and authenticity of digital material. It does not directly decide source code discovery, but its evidentiary principles may apply to electronic records produced during such proceedings.

Procedure and judicial considerations

A party seeking source code discovery should identify the disputed software, relevant portions of the code and the legal issue requiring examination. A general request for an opponent's entire software repository may be rejected as excessive or disproportionate.

Courts may consider the following factors:

Relevance: Whether the source code relates directly to the disputed functionality, infringement or technical defect.

Necessity: Whether the issue can be resolved through less intrusive evidence.

Proportionality: Whether the expected evidentiary value justifies the cost and burden of discovery.

Confidentiality: Whether disclosure would reveal trade secrets or commercially sensitive information.

Security: Whether access could expose vulnerabilities or create risks of unauthorised use.

Protective measures may include independent expert inspection, restricted access, confidentiality undertakings, secure examination facilities, redaction and limitations on copying or retaining code.

Challenges and safeguards

Source code discovery presents challenges because software may contain third-party libraries, confidential algorithms and security credentials. Unrestricted disclosure can cause commercial harm or expose systems to cyber risks. Conversely, excessive secrecy may prevent a party from proving infringement or challenging defective automated decisions.

A balanced judicial approach should therefore permit access only to material necessary for resolving the dispute. Independent technical experts can examine the relevant code and submit reports without disclosing unrelated proprietary information. Courts should also establish clear rules concerning storage, copying, access and destruction of disclosed material.

Conclusion

Discovery of source code in litigation is an increasingly important mechanism for resolving technology-related disputes. Indian civil procedure, commercial litigation rules, copyright law and electronic evidence provisions provide a legal foundation for obtaining relevant software material. However, Indian law does not establish an automatic right to inspect an opponent's complete source code. Courts must assess relevance, necessity, proportionality, confidentiality and security before ordering discovery. A controlled disclosure process supported by independent technical examination can protect both the interests of justice and legitimate software ownership rights.