ctxlineage 0.1.0__tar.gz

ctxlineage-0.1.0/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,29 @@
+name: Bug report
+description: Something broke or captured/rendered incorrectly
+labels: [bug]
+body:
+  - type: textarea
+    id: what
+    attributes:
+      label: What happened?
+      description: Include the command or code you ran and what went wrong.
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: What did you expect?
+    validations:
+      required: true
+  - type: textarea
+    id: repro
+    attributes:
+      label: Minimal reproduction
+      description: Smallest snippet / events.jsonl excerpt that shows the problem (redact prompts!).
+  - type: input
+    id: version
+    attributes:
+      label: Versions
+      placeholder: ctxlineage 0.1.0 / openai 2.41.1 / Python 3.12 / macOS
+    validations:
+      required: true

ctxlineage-0.1.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security report
+    url: https://github.com/ctxlineage/ctxlineage/blob/main/SECURITY.md
+    about: Please report vulnerabilities privately — see SECURITY.md (do not open a public issue).

ctxlineage-0.1.0/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,20 @@
+name: Feature request
+description: Suggest an improvement
+labels: [enhancement]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: What are you trying to see or do that you currently cannot?
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed solution
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Note the roadmap lives in the milestone issues; off-roadmap requests may be closed per the maintenance policy.

ctxlineage-0.1.0/.github/dependabot.yml

@@ -0,0 +1,12 @@
+version: 2
+updates:
+  - package-ecosystem: pip
+    directory: /
+    schedule:
+      interval: weekly
+    labels: [dependencies]
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+    labels: [dependencies]

ctxlineage-0.1.0/.github/labels.yml

@@ -0,0 +1,37 @@
+# Source of truth for repo labels (synced by .github/workflows/sync-labels.yml)
+- name: bug
+  color: d73a4a
+  description: Something is broken
+- name: enhancement
+  color: a2eeef
+  description: Feature or improvement
+- name: documentation
+  color: 0075ca
+  description: Docs only
+- name: dependencies
+  color: 0366d6
+  description: Dependency updates
+- name: good first issue
+  color: 7057ff
+  description: Small, well-scoped, newcomer-friendly
+- name: help wanted
+  color: 008672
+  description: Community contribution welcome
+- name: wontfix
+  color: ffffff
+  description: Out of scope / off-roadmap
+- name: duplicate
+  color: cfd3d7
+  description: Already tracked elsewhere
+- name: milestone
+  color: 1FBFAE
+  description: v1 milestone tracking issue
+- name: human-action
+  color: D93F0B
+  description: Requires the maintainer (accounts, uploads, announcements)
+- name: backlog
+  color: C5DEF5
+  description: Post-v1 ideas, not scheduled
+- name: discussion
+  color: 8250DF
+  description: Discussion topic for a dedicated session with the maintainer

ctxlineage-0.1.0/.github/pull_request_template.md

@@ -0,0 +1,13 @@
+## What
+
+<!-- one or two sentences -->
+
+## Related
+
+<!-- issue number, e.g. part of #4 / closes #12 -->
+
+## Checklist
+
+- [ ] Tests added/updated (`uv run pytest`)
+- [ ] Lint clean (`uv run ruff check . && uv run ruff format --check .`)
+- [ ] Commits signed off (`git commit -s`, DCO)

ctxlineage-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,30 @@
+name: release
+# Tag-driven PyPI release via OIDC Trusted Publishing (no API token secrets).
+# Requires: PyPI pending publisher configured for this repo/workflow, and a
+# GitHub environment named `pypi`. Inert until a v* tag is pushed.
+on:
+  push:
+    tags: ["v*"]
+permissions:
+  contents: read
+jobs:
+  verify:
+    if: github.repository == 'ctxlineage/ctxlineage'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+      - run: uv sync
+      - run: uv run ruff check .
+      - run: uv run pytest -q
+  publish:
+    needs: verify
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+      - run: uv build
+      - uses: pypa/gh-action-pypi-publish@release/v1

ctxlineage-0.1.0/.github/workflows/sync-labels.yml

@@ -0,0 +1,16 @@
+name: sync-labels
+on:
+  push:
+    branches: [main]
+    paths: [.github/labels.yml]
+permissions:
+  issues: write
+jobs:
+  sync:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: crazy-max/ghaction-github-labeler@v6
+        with:
+          yaml-file: .github/labels.yml
+          skip-delete: true

ctxlineage-0.1.0/.github/workflows/test.yml

@@ -0,0 +1,51 @@
+name: test
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  schedule:
+    # Weekly run against the latest SDK versions (PLAN.md §12: catch upstream
+    # openai/anthropic changes early).
+    - cron: "0 6 * * 1"
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+      - run: uv sync
+      - run: uv run ruff check .
+      - run: uv run ruff format --check .
+      - name: Package builds
+        run: uv build
+
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install dependencies
+        run: |
+          if [ "${{ github.event_name }}" = "schedule" ]; then
+            uv sync --upgrade
+          else
+            uv sync
+          fi
+      - name: Run tests
+        run: uv run pytest -v --cov=ctxlineage --cov-report=term-missing --cov-report=xml
+      # Coverage upload only once per matrix (drt pattern); tokenless upload
+      # via the org-installed Codecov app (#12).
+      - name: Upload coverage
+        if: matrix.python-version == '3.13'
+        uses: codecov/codecov-action@v7
+        with:
+          files: coverage.xml
+          fail_ci_if_error: true

ctxlineage-0.1.0/.gitignore

@@ -0,0 +1,39 @@
+# Local working drafts (Japanese planning doc — canonical English version: docs/PLAN.md)
+base_plan.md
+
+# ctxlineage's own capture output
+.ctxlineage/
+
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+dist/
+build/
+.venv/
+venv/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+
+# Node / frontend
+node_modules/
+frontend/dist/
+
+# Tooling / editors
+.serena/
+.claude/
+.idea/
+.vscode/
+.DS_Store
+.coverage
+
+# Playwright MCP artifacts
+.playwright-mcp/
+
+# Generated report artifacts
+ctxlineage-report.html
+coverage.xml

ctxlineage-0.1.0/CHANGELOG.md

@@ -0,0 +1,41 @@
+# Changelog
+
+All notable changes to this project are documented here.
+Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versioning:
+[SemVer](https://semver.org/spec/v2.0.0.html) (pre-1.0: breaking changes may
+land in minor versions).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-07-17
+
+First public release.
+
+### Added
+- Capture core: `ctxlineage.init()` auto-instruments the **openai** (Chat
+  Completions + Responses API) and **anthropic** (Messages) SDKs — sync,
+  async, and streaming — into append-only `.ctxlineage/events.jsonl`
+  (versioned JSON Schema).
+- Explicit **span/tag API**: `with ctxlineage.span(...) as sp: sp.tag(name,
+  content, source=..., transform=...)` for context provenance.
+- **Report** (`ctxlineage report`): one self-contained HTML file with four
+  views — Overview, Calls (context-window anatomy), Chain (session flow),
+  Graph (sources → elements → calls lineage with impact tracing) — plus
+  client-side search, light/dark themes, i18n-safe rendering.
+- Segment matching (exact → partial → honest untagged) with a visible tag
+  match rate; lineage edge inference (output→input, same-span) computed in
+  the report backend.
+- Coexistence test matrix with the Langfuse OpenAI drop-in.
+- **Redaction**: `ctxlineage report --redact PATTERN` (repeatable regex;
+  applied after matching so stats stay honest, disclosed in the report) and
+  capture-side `ctxlineage.init(redact_fields=[...])` field masking (secrets
+  never reach `events.jsonl`).
+- Read-only **MCP server** (`ctxlineage[mcp]` extra, `ctxlineage-mcp` entry
+  point): list_sessions / get_call / get_lineage / generate_report over the
+  same JSONL.
+- Anthropic Messages rendered honestly in the report: top-level `system`
+  prompt, `tool_use` / `tool_result` blocks, thinking-block markers, streamed
+  assembly, and cache-token folding into the window figures.
+- Runnable examples (`examples/rag_app.py`, `examples/agent_app.py`,
+  `examples/anthropic_app.py`, all with a keyless `--mock` mode) and a
+  `ctxlineage-instrument` agent skill.

ctxlineage-0.1.0/CLAUDE.md

@@ -0,0 +1,51 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## What this is
+
+ctxlineage: a local-first Python library that records every LLM call (OpenAI / Anthropic SDKs, auto-instrumented via monkey-patch) to an append-only `.ctxlineage/events.jsonl`, then renders a **single static HTML report** (Call Anatomy + Lineage Graph views). Zero server, zero DB, no external data transmission — ever.
+
+**Current state: v0.1.0 (first public release).** All of M1–M4 shipped: capture (openai + anthropic, sync/async/streaming), the four-view report, the span/tag lineage pipeline, the MCP server, redaction, and runnable examples. Build/test: `uv sync --all-extras`, `uv run pytest`, `uv run ruff check . && uv run ruff format .`. Next: v0.2 = context contract testing (#14) + coding-agent session import (#57).
+
+## Required workflow
+
+- [docs/PLAN.md](docs/PLAN.md) is the canonical spec. Read it before implementing anything.
+- Before coding a feature, write a detailed implementation plan under `docs/plans/YYYY-MM-DD-<feature>.md`.
+- **Non-Goals (PLAN.md §5) are hard guardrails** — do not implement: SaaS/hosting/accounts, evals, prompt versioning, persistent DBs (incl. SQLite; JSONL is the store), non-Python SDKs, LLM proxying (never rewrite/forward requests).
+- TODOs live in GitHub issues (`ctxlineage/ctxlineage`), not in local files. Milestones M1–M4 are issues #1–#4; each milestone must be independently demoable.
+- TDD with pytest; SDK patches are tested against mocked HTTP (respx).
+
+## Maintainer commands (`.claude/commands/`)
+
+Repo-scoped slash commands for the maintainer's own workflow (not end-user
+features), adapted from the drt-hub operations playbook:
+
+- `/ctxlineage-release-check` — version/doc consistency sweep, then the
+  tag → Trusted Publishing flow.
+- `/ctxlineage-review-pr` — PR review keyed on ctxlineage's load-bearing rules
+  (host-app safety, no proxying, honest data, self-contained report, Non-Goals).
+- `/ctxlineage-triage` — open PR/issue triage and release-readiness check.
+
+## Conventions
+
+- **Everything in the repo is English** (code, comments, docs, issues, commits) even when the conversation with the user is in Japanese.
+- `base_plan.md` (Japanese) is a local, gitignored draft — never commit it; docs/PLAN.md is the source of truth.
+- Commits use the personal identity `K.Masuda <me@masukai.dev>` (already set in repo-local git config). License is Apache-2.0 with DCO; never copy-paste external code — take it as a dependency instead.
+- Keep the public API surface and the SDK patch layer minimal (low-maintenance is an explicit design goal); unknown SDK fields pass through into `payload` rather than being modeled.
+
+## Architecture (planned, PLAN.md §6)
+
+Three loosely-coupled layers sharing one artifact, the JSONL event log:
+
+1. **Capture** — `ctxlineage.init()` monkey-patches openai/anthropic SDKs (wrapt); optional explicit `span()`/`tag()` API adds metadata. Writes 1 event per line to `.ctxlineage/events.jsonl`. Streaming support is mandatory.
+2. **Report builder** — `ctxlineage report` CLI parses the JSONL, normalizes sessions/calls/elements/edges, runs segment matching (exact → partial → "untagged" fallback, match rate shown honestly) and lineage edge inference, then injects JSON into a prebuilt HTML template.
+3. **MCP server** (`src/ctxlineage_mcp/`, FastMCP/stdio) — read-only tools over the same JSONL.
+
+The event schema (`schema/`, versioned JSON Schema) is language-agnostic by design — it is the contract between all layers and future non-Python SDKs.
+
+The report frontend is **server-rendered by Python** (decided 2026-07-16 — no React/Vite, no node toolchain): templates, vanilla JS, and a single CSS-token block live as package resources under `src/ctxlineage/_report/`; the lineage graph is emitted as static SVG whose colors reference CSS custom properties. Light and dark mode are both mandatory (default follows `prefers-color-scheme`, manual toggle persisted). The HTML must open offline (no CDN references). Design reference: the maintainer's drt-hub/drt `drt docs` (deterministic layout engine, reserved-gutter edge routing) and the agreed mockups in `docs/design/m2-mockups/`. Report UI palette: Ink `#252B33` × Lineage Teal `#1FBFAE`.
+
+## Stack
+
+Python 3.10+, `uv` + `hatchling`, src layout. Minimal runtime deps: `wrapt`, `tiktoken` (prefer real `usage` values over estimates). CLI ships as `ctxlineage` with alias `ctxl`.

ctxlineage-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,40 @@
+# Contributing
+
+Thanks for your interest! ctxlineage is a deliberately low-maintenance,
+single-maintainer project — small, focused contributions land fastest.
+
+## Setup
+
+```bash
+git clone https://github.com/ctxlineage/ctxlineage && cd ctxlineage
+uv sync                                  # installs everything (Python 3.10+)
+uv run pytest                            # tests (hermetic — no network)
+uv run ruff check . && uv run ruff format .   # lint / format
+```
+
+Useful while hacking on the report UI:
+
+```bash
+uv run python examples/generate_demo_events.py /tmp/demo
+CTXLINEAGE_DIR=/tmp/demo uv run ctxlineage report --open
+```
+
+## Ground rules
+
+- **DCO, not CLA.** Sign off every commit: `git commit -s`
+  (adds `Signed-off-by`, certifying [developercertificate.org](https://developercertificate.org/)).
+- **Never copy-paste external code** — take it as a dependency instead.
+- **TDD**: changes come with tests; SDK patches are tested against mocked HTTP
+  (respx). The suite must stay hermetic (no network).
+- Everything in the repo is English.
+- Pre-1.0, minor versions may contain breaking changes (CLI output, public
+  API, event schema constraints). The event schema (`schema/`) is the
+  versioned contract — additive changes only within a schema version.
+
+## Scope
+
+The roadmap lives in the milestone issues. Non-Goals
+([docs/PLAN.md](docs/PLAN.md) §5) are hard guardrails: no SaaS, no evals, no
+prompt management, no persistent DBs, no LLM proxying. Off-roadmap issues and
+PRs may be closed without much ceremony — please open an issue before large
+changes.

ctxlineage-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.