Where should I document changes made to the original code?

The skill recommends adding prominent notices directly in the modified files for small changes, or using a comprehensive CHANGELOG/CHANGES file for larger forks.

What are the core requirements for redistributing Apache 2.0 code?

You must include a copy of the license, retain all original copyright and attribution notices, and provide prominent notices in any files you have modified.

Is this skill a substitute for legal advice?

No, this skill provides procedural guidance based on the license text. Users should consult with legal counsel for specific compliance audits or complex licensing questions.

How does this skill help with NOTICE files?

It provides a checklist to ensure that if the original work had a NOTICE file, your derivative work includes those attributions in a way that complies with Section 4d.

Apache License 2.0 Compliance Guide

Name: Apache License 2.0 Compliance Guide
Author: WarrenZhu050413

byWarrenZhu050413

•

安全与测试

Ensures derivative software projects adhere to Apache License 2.0 requirements for attribution, documentation, and redistribution.

关于

This skill provides a comprehensive framework for developers working with Apache-licensed codebases, guiding Claude through the critical steps of maintaining legal compliance. It streamlines the process of preserving original copyright notices, managing NOTICE and LICENSE files, and properly documenting code modifications as required by Section 4 of the license. Whether you are forking a repository, incorporating open-source snippets, or preparing a commercial release, this skill ensures that best practices for attribution and change documentation are followed to protect the integrity of the project and its contributors.

主要功能

Automated shell commands for license and copyright verification
Validation checklists for NOTICE and LICENSE file placement
Attribution preservation guidelines for Section 4 requirements
Standardized templates for prominent in-file change notices
Step-by-step compliance workflow for derivative works
5 GitHub stars

使用场景

Integrating open-source modules into a proprietary codebase with proper attribution
Forking an Apache-licensed project for commercial or private redistribution
Auditing a repository's licensing files and headers before a production release

关于

主要功能

Automated shell commands for license and copyright verification
Validation checklists for NOTICE and LICENSE file placement
Attribution preservation guidelines for Section 4 requirements
Standardized templates for prominent in-file change notices
Step-by-step compliance workflow for derivative works
5 GitHub stars

使用场景

Integrating open-source modules into a proprietary codebase with proper attribution
Forking an Apache-licensed project for commercial or private redistribution
Auditing a repository's licensing files and headers before a production release