OfficeCLI License: Apache 2.0 Terms and Compliance Guide

OfficeCLI is distributed under the Apache License 2.0, a permissive open-source license that grants perpetual, worldwide rights to use, modify, and distribute the software provided you include the license text and copyright notices.

OfficeCLI from the iOfficeAI/OfficeCLI repository provides command-line tools for document automation. Before integrating this tool into your projects, understanding the OfficeCLI license terms ensures you remain compliant with open-source requirements. The Apache 2.0 license offers flexibility for both personal and commercial use while maintaining necessary attribution standards.

What License Does OfficeCLI Use?

OfficeCLI uses the Apache License 2.0. You can find the complete legal text in the repository's LICENSE file at the root level: LICENSE.

This permissive license allows you to:

• Use the software for any purpose, including commercial applications
• Modify the source code to fit your needs
• Distribute original or modified versions
• Receive patent contributions from the project

According to the iOfficeAI/OfficeCLI source code, the license metadata also appears in npm/package.json, ensuring the Node.js package registry correctly identifies the Apache 2.0 classification.

Apache 2.0 Compliance Requirements

When using OfficeCLI in your own projects, the Apache License 2.0 imposes specific obligations to maintain open-source integrity.

Include the License Text

Any redistribution of OfficeCLI, whether modified or unmodified, must include a copy of the LICENSE file. This applies to both source code distributions and compiled binaries.

Preserve Copyright Notices

You must retain all existing copyright notices and attribution markers found in the original files. The standard header format references "OfficeCLI (https://OfficeCLI.AI)" and the copyright holder.

Document Your Changes

If you modify OfficeCLI source files such as officecli.js or install.sh, you must clearly state what changes you made. This requirement helps recipients distinguish your alterations from the original implementation.

Locating License Information in the Repository

The iOfficeAI/OfficeCLI repository organizes licensing information across several key files:

• LICENSE – Contains the full Apache License 2.0 text
• README.md – Provides overview and usage instructions
• npm/package.json – Node.js metadata confirming the license field
• npm/officecli.js – Main CLI entry point carrying license headers
• install.sh – Installation script for Unix-like systems
• install.ps1 – Installation script for Windows PowerShell

How to Reference the OfficeCLI License in Your Projects

When incorporating OfficeCLI into your own distributions, use these patterns to maintain compliance.

Add the SPDX identifier to your scripts that import OfficeCLI:

# SPDX-License-Identifier: Apache-2.0

# Copyright (c) 2026 OfficeCLI (https://OfficeCLI.AI)

import officecli

# Your implementation continues...

When creating distribution archives, include the license file alongside the source:

# Package OfficeCLI with proper attribution

tar czf officecli-package.tar.gz \
  --transform 's,^,officecli/,' \
  LICENSE README.md src/ scripts/

This approach ensures you satisfy the Apache 2.0 redistribution requirements while clearly documenting the software's origin.

Summary

• OfficeCLI is licensed under Apache License 2.0, found in the repository root LICENSE file.
• The license permits commercial use, modification, and distribution without requiring source code disclosure of your own applications.
• Compliance requires including the license text, preserving copyright notices, and documenting any modifications to original files.
• License metadata appears in npm/package.json and source headers throughout the codebase.

Frequently Asked Questions

Is OfficeCLI free for commercial use?

Yes. The Apache License 2.0 grants you a worldwide, royalty-free right to use OfficeCLI in commercial products. You can sell applications built with OfficeCLI or offer it as part of paid services without licensing fees, provided you comply with the attribution requirements outlined in the LICENSE file.

Do I need to open-source my code if I use OfficeCLI?

No. The Apache License 2.0 is a permissive license that does not require you to distribute your own application source code. Unlike copyleft licenses such as GPL, you can build proprietary software using OfficeCLI while keeping your code private, as long as you include the OfficeCLI license and copyright notices.

Where is the license file located in the OfficeCLI repository?

The full license text resides at LICENSE in the repository root. You can view it directly at https://github.com/iOfficeAI/OfficeCLI/blob/main/LICENSE. Additionally, the npm/package.json file references the Apache 2.0 license to confirm the Node.js package classification.

What happens if I modify OfficeCLI source code?

If you modify files such as officecli.js or install.sh, you must include a prominent notice stating that you changed the files. The Apache License 2.0 requires documentation of modifications so recipients can distinguish original work from your alterations, though you may license your modifications under any compatible terms.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}