License & attribution¶

ast-outline uses two separate licenses for two different kinds of work:

What	License	File
Source code (v0.6.0+)	Apache 2.0	`LICENSE`
Source code (≤ v0.5.3)	MIT	`LICENSE-MIT`
Documentation & prose (this site, READMEs, CLI help text, prompt files, digest legend)	CC BY 4.0	`LICENSE-DOCS`

All three are permissive — fork, use commercially, port to other languages, ship in a product. The split exists so attribution requirements are explicit for each kind of content. Forks of the 0.5.x tree may continue under MIT; new development happens under Apache 2.0.

If you reuse the code (v0.6.0+)¶

Keep the LICENSE (Apache 2.0) and NOTICE files in your distribution. Apache 2.0 §4 requires you to:

include the LICENSE file
include the NOTICE file in any "NOTICE" text file distributed with your work
carry forward attribution notices (do not strip the copyright header)
in modified files, add a notice stating that you changed them

If you reuse the prose¶

If your project copies non-trivial portions of this documentation — paragraphs, the workflow snippets, the digest legend, the marker vocabulary, the # note: CLI convention's wording — CC BY 4.0 requires visible attribution. Use this format (verbatim or equivalent):

Based on ast-outline by Dmitrii Zaitsev (dim-s), licensed under CC BY 4.0.

Place it where users will see it (typically the README of your derivative work).

Trademark¶

ast-outline™ is an unregistered trademark of Dmitrii Zaitsev (dim-s), used to identify the original project at https://github.com/ast-outline/ast-outline. Apache License 2.0 §6 explicitly excludes any grant of trademark rights.

Forks, language ports, and rebranded distributions must use a different name to avoid user confusion. "Inspired by ast-outline" or "based on ast-outline" wording in your README is fine and encouraged; using ast-outline itself as your project / package / binary name is not.

If you maintain a published package called ast-outline on any registry (crates.io, npm, PyPI, Homebrew, etc.) that is not the project at the URL above, please rename it.

Contributing¶

Issues and pull requests are welcome at the GitHub repository.

By contributing, you agree that your contributions will be licensed under the project's licenses (Apache 2.0 for code, CC BY 4.0 for documentation).