evalvitals 0.1.0__py3-none-any.whl

evalvitals/__init__.py

@@ -0,0 +1,112 @@
+"""EvalVitals — failure case analysis for LLMs and VLMs.
+
+A model is built once from a **spec** (identity, in :mod:`evalvitals.specs`) and a
+**backend** (runtime: ``hf_local`` / ``api`` / ``vllm_offline``); the backend
+determines the capability set.  Analyzers are sklearn-style estimators matched to
+models by capability.
+
+Equivalent ways to run an analysis:
+
+0. Bring your own model — wrap an already-loaded HF model + tokenizer::
+
+    import evalvitals
+    from transformers import AutoModelForCausalLM, AutoTokenizer
+    from evalvitals.analyzers.lens.logit_lens import LogitLensAnalyzer
+
+    m = AutoModelForCausalLM.from_pretrained("my-org/my-llama")
+    tok = AutoTokenizer.from_pretrained("my-org/my-llama")
+    model = evalvitals.wrap(m, tok)                         # captum-style on-ramp
+    result = LogitLensAnalyzer().run(model, "The capital of France is")
+
+1. Curated checkpoints — build a model from the registry by key::
+
+    import evalvitals
+    from evalvitals.analyzers.attention.summary import AttentionAnalyzer
+
+    model = evalvitals.load("qwen2.5-7b-instruct")          # spec key
+    result = AttentionAnalyzer(top_k=5).run(model, "The capital of France is")
+    print(result.summary())
+
+2. Config-driven — declare model + analysis in YAML::
+
+    from evalvitals import load_config, run
+
+    config = load_config("configs/qwen_attention.yaml")
+    result = run(config, "The capital of France is")
+
+3. Hybrid convenience shim (auto-derived from capabilities)::
+
+    result = model.call_attention("The capital of France is")
+
+4. Explicit engine — pick the backend yourself::
+
+    from evalvitals.models import compose
+    model = compose("qwen2.5-7b-instruct", "hf_local", want={evalvitals.Capability.ATTENTION})
+"""
+
+# Importing these populates the registry (models + analyzers self-register).
+import evalvitals.analyzers as _analyzers  # noqa: E402,F401
+from evalvitals.config import AnalysisConfig, load_config
+from evalvitals.core import (
+    Analyzer,
+    Capability,
+    CaseBatch,
+    FailureCase,
+    Model,
+    Result,
+    registry,
+)
+from evalvitals.core.tool import Tool, ToolCall
+from evalvitals.models import Agent, RuntimeConfig, compose, load, load_model, wrap
+from evalvitals.specs import get_spec, list_specs
+
+__version__ = "0.1.0"
+__all__ = [
+    "load",
+    "load_config",
+    "load_model",
+    "wrap",
+    "compose",
+    "RuntimeConfig",
+    "Agent",
+    "Tool",
+    "ToolCall",
+    "get_spec",
+    "list_specs",
+    "run",
+    "AnalysisConfig",
+    "Model",
+    "Analyzer",
+    "Result",
+    "FailureCase",
+    "CaseBatch",
+    "Capability",
+    "registry",
+]
+
+
+def run(config: AnalysisConfig, data, **kwargs):
+    """Run the analysis declared by *config* on *data*.
+
+    Equivalent to::
+
+        analyzer = registry.analyzers.get(config.analysis)(**config.analysis_kwargs)
+        analyzer.run(load_model(config.model), data)
+
+    Args:
+        config: Loaded :class:`AnalysisConfig` (see :func:`load_config`).
+        data:   ``str | FailureCase | CaseBatch | iterable`` to analyse.
+        **kwargs: Override or extend ``config.analysis_kwargs`` at call time.
+
+    Returns:
+        A :class:`~evalvitals.core.result.Result` subclass.
+    """
+    # Back-compat: tolerate a leading "call_" in the config (old style).
+    name = config.analysis
+    if name.startswith("call_"):
+        name = name[len("call_"):]
+
+    analyzer_cls = registry.analyzers.get(name)
+    analyzer = analyzer_cls(**{**config.analysis_kwargs, **kwargs})
+    model = load_model(config.model)
+    return analyzer.run(model, data)

evalvitals/agent_assets/__init__.py

@@ -0,0 +1,2 @@
+"""Bundled runtime assets for EvalVitals agents."""
+

evalvitals/agent_assets/skills/README.md

@@ -0,0 +1,28 @@
+# Bundled Agent Skills
+
+Agent Skills vendored into the package so they travel with the repo (both
+`git clone` and `pip install`) and are auto-discovered by `evalvitals explore`
+on the **claude** / **agy** backends. They style the figures the exploratory
+coding agent writes under `figures/` — they do **not** affect the host-rendered,
+deterministic chart specs (`render_chart_specs`).
+
+Each `explore` run vendors these into its sandbox at
+`<workdir>/.claude/skills/<name>/`, which an `--add-dir <workdir>` Claude Code /
+agy run discovers automatically.
+
+## nature-figure
+
+Submission-grade Nature/high-impact-journal matplotlib/ggplot figure workflow.
+
+- **Source:** https://github.com/Yuan1z0825/nature-skills (`skills/nature-figure`)
+- **License:** Apache-2.0 — see [`nature-figure/LICENSE`](nature-figure/LICENSE).
+- **Trimmed:** only the functional core is vendored (SKILL.md, manifest.yaml,
+  `static/`, `references/`, ~176 KB). The upstream `assets/` demo galleries
+  (~30 MB of example PNGs and figures4papers scripts) are **omitted** to keep
+  the repo lean; fetch them from the source repo if you want the demo galleries.
+
+## Disabling / overriding
+
+- `evalvitals explore … --no-skills` skips bundled skills for a run.
+- `evalvitals explore … --skill /path/to/other-skill` adds more skill dirs.
+- `--allow-skills` also lets globally-installed `~/.claude/skills` be used.

evalvitals/agent_assets/skills/eval-chart-style/SKILL.md

@@ -0,0 +1,113 @@
+---
+name: eval-chart-style
+version: 0.2.0
+description: >
+  Chart-type policy + house style for FAIL-vs-PASS LLM/VLM eval analysis
+  figures. Use whenever you plot eval results inside an EvalVitals analysis
+  sandbox — matplotlib PNGs under figures/ or deterministic chart specs — and
+  the point is to NOT default to a bar chart. This skill decides WHAT chart to
+  draw and the semantic palette; for journal-grade polish (fonts, export, QA)
+  additionally apply the nature-figure skill on the figures you draw.
+---
+
+# Eval Chart Style
+
+House chart-type policy for FAIL-vs-PASS eval analysis. It exists to stop three
+recurring failures: plotting a **mean as a bar** when the claim depends on the
+*distribution*; inconsistent FAIL/PASS colors between charts; and raw machine
+output (column ids, `pandas.cut` edges) leaking into axes and titles.
+
+It is the agent-side counterpart of the host module
+`evalvitals.analysis.eval_viz_theme` (plotly). If plotly is available you may
+`from evalvitals.analysis import eval_viz_theme as viz; viz.apply()` and use its
+builders; otherwise apply the rules below directly in matplotlib.
+
+## 0. Chart-type policy (the most important rule)
+
+**A bar's filled area means "amount accumulated from zero." Use bars only for
+counts.** For a mean, a proportion, a measurement, or an effect size, a bar
+hides the distribution and fakes certainty. Pick by *what the reader must see*:
+
+| What you're showing | DON'T | DO |
+|---|---|---|
+| Discrete class counts (FAIL/PASS n) | — | grouped bars, n annotated |
+| A continuous signal across outcomes | two-bar "mean by outcome" | violin/box + jittered points, one panel |
+| Several signals' effects ranked | green/grey bars | horizontal **dot + CI** (forest) |
+| Fail rate vs a continuous signal | bare binned bars | binned rate **line** (or logistic curve) + n per bin |
+| Two continuous signals jointly | scatter squeezed small | full-width scatter colored by outcome (+ marginals if easy) |
+| Rates across two categoricals | grouped bars ×k | **heatmap** with annotated cells |
+| Distribution shape / tail claims | histogram only | ECDF or KDE overlay by outcome |
+| Paired/intervention outcomes | two bars | paired slope or discordant counts |
+
+Why distributions: with small FAIL n a mean is outlier-driven, and any
+"two sub-populations" story is a *bimodality claim* — a bar can show neither.
+
+**Suppress degenerate charts.** A binary/constant signal's fail-rate curve
+collapses to one or two dots — don't render it; note it in caveats instead.
+Aim for *diversity that matches the data*: across the figure set prefer
+violin + ECDF + heatmap + forest + scatter over eight bar charts.
+
+## 1. Semantic palette (color encodes role, not decoration)
+
+Lock these and reuse in every figure — the reader must never re-learn who is who:
+
+- FAIL → warning red `#C0413B`; PASS → neutral slate `#5B7A99` (same side, same
+  hue in every chart).
+- Supported / survived-adjudication → green `#2E8B6F`; inconclusive → grey
+  `#B8BCC2`. Unknown significance defaults to grey, never green.
+- Leakage/sanity signals → muted grey `#9AA0A6`, never a "winner" color.
+
+Non-outcome dimensions get their own color logic — do NOT squeeze every panel
+into the FAIL/PASS pair plus grey:
+
+- **Categorical series** (checkpoint/model lines, object classes, several
+  signals overlaid on one axis): use this series order, in order —
+  `#0F4D92` deep blue, `#8BCF8B` green, `#B64342` red\*, `#42949E` teal,
+  `#9A4D8E` violet, `#CFCECE` neutral grey. (\*Skip the red slot whenever
+  FAIL-red already appears on the same panel — the outcome hue must stay
+  unambiguous.)
+- **Ordered dimensions** (model size 2B→4B→8B, ordered bins, dose/strength
+  ladders): ONE hue with a luminance/alpha ramp (light → dark = small →
+  large), not distinct hues — the ordering should be readable from the ramp
+  alone. E.g. three blues `#B4C0E4 → #7884B4 → #0F4D92`.
+- Precedence: semantic role colors always win — wherever the outcome appears,
+  FAIL/PASS keep their hues; the series/ramp colors are for panels sliced by
+  something other than the outcome. Heatmaps: diverging data (signed effects)
+  → Red-Blue diverging around 0; magnitude-only data → a single-hue
+  sequential ramp.
+
+Never print a raw column id (`generated_probe1_false_detection`) on an axis,
+tick, or title — use a short human alias (≤ ~12 chars) and keep the raw name in
+a caption/hover/table only.
+
+## 2. Layout
+
+- Distribution plots and scatters get full width; never squeeze a scatter into
+  a narrow subplot.
+- One title per chart; don't repeat the section heading inside the figure.
+- Label every axis with the *short* name + unit; annotate the zero/reference
+  line on effect axes.
+
+## 3. Numbers and bins
+
+- effects/correlations → 2 dp; p-values/statistics → 3 dp; percents → integer
+  (`41%`); counts → integer.
+- **Never display raw `pandas.cut` edges** (`(113.844, 233.066]`). Render
+  human bins: `114–233`. Annotate per-bin n when bins are sparse.
+
+## 4. Statistical honesty
+
+- A signal that *is* the outcome re-measured (fail rate 1.00/0.00, effect ≈
+  perfect) is target leakage: demote it to a greyed sanity-check, never rank
+  it #1.
+- Pick ONE primary effect metric for headline figures; relegate the rest to a
+  table, and label which metric every axis shows.
+- Descriptive is descriptive: no "confirmed/validated" wording in titles.
+
+## Scope note for EvalVitals sandboxes
+
+Host-rendered chart *specs* stay deterministic (`kind` ∈ bar/line/scatter with
+pre-aggregated CSVs) — apply §1/§3 to their data and titles. The chart-type
+diversity of §0 lives in the PNGs you draw under `figures/` — that is where
+violins, ECDFs, heatmaps, forests, and paired-slope figures belong. Styling
+only: never change the data, the analysis, or the final result JSON.

evalvitals/agent_assets/skills/evalvitals-report-ui/SKILL.md

@@ -0,0 +1,116 @@
+---
+name: evalvitals-report-ui
+description: Generate EvalVitals exploratory results that read like diagnostic reports, not raw feature dumps.
+---
+
+# EvalVitals Report/UI Contract
+
+Use this skill whenever you produce EvalVitals exploratory analysis JSON,
+dashboard-ready artifacts, chart specs, or diagnostic report text.
+
+## Audience
+
+The reader is evaluating a model failure mode. They should not need to know
+internal probe ids, generated column names, or implementation details to
+understand the result.
+
+## Stage Semantics
+
+Use these stage names consistently:
+
+- **M1 — Measurement:** frozen per-case data, analyzer/probe outputs, attention
+  maps, and derived signals. Dashboard role: Problem Setting.
+- **M2 — Confirmatory analysis:** statistical comparisons of FAIL vs PASS,
+  effect sizes, CIs, e-values/e-BH, and deterministic charts. Dashboard role:
+  Analysis.
+- **M3 — Hypothesis generation:** falsifiable explanations formed from M2
+  evidence plus exploratory context. Dashboard role: Hypotheses.
+- **M4 — Mechanism test:** targeted experiments/interventions that test whether
+  a mechanism is real. Dashboard role: decision evidence.
+- **M5 — Repair/surgery test:** proposed repair/fix outcomes and regression
+  checks. Dashboard role: final action gate.
+
+Every dashboard/report should make clear which stage produced each claim,
+chart, hypothesis, or artifact.
+
+## Dashboard Storyboard
+
+Do not produce an artifact dump. Produce a three-panel reader path:
+
+1. **Problem Setting (M1 + run context)**
+   - What user question is being answered?
+   - What data/cases were provided?
+   - What is FAIL vs PASS?
+   - Which signals/analyzers are available?
+
+2. **Analysis (M2)**
+   - For every analysis method, write: `method`, `evidence/chart`, `takeaway`.
+   - Put the main chart next to the method it supports.
+   - Put table details below the chart, not before the takeaway.
+
+3. **Hypotheses & Artifacts (M3-M5)**
+   - List hypotheses only after M2 evidence.
+   - Link each hypothesis to cited charts/signals.
+   - Summarize M4/M5 test or fix outcomes.
+   - Keep raw artifacts in expandable drill-down sections.
+
+Emit the reader path as `dashboard_storyboard` in the final JSON. The dashboard
+renderer is intentionally stable and should only render this artifact. The
+agent, not the Streamlit host, owns the run-specific narrative.
+
+Required storyboard panel shape:
+
+```json
+{
+  "id": "problem_setting | analysis | hypotheses_artifacts",
+  "title": "Human panel title",
+  "stages": ["M1"],
+  "summary": "One paragraph written for the user",
+  "items": ["method -> evidence -> takeaway bullets"],
+  "artifact_refs": ["candidate_signals", "charts"]
+}
+```
+
+## Required Output Discipline
+
+- Every `candidate_signals` item must include:
+  - `name`: stable machine id, snake_case, suitable for recipes and joins.
+  - `display_name`: short human label, suitable for dashboard titles.
+  - `rationale`: one sentence in domain language.
+  - `suggested_test`: what would confirm or refute it.
+- Every chart spec should include:
+  - `name`: stable machine id.
+  - `title` or `display_name`: human-readable, no raw probe/generated id unless
+    no interpretation is known.
+- Every `visual_plan` item should include a readable `question` and avoid raw
+  field names in the user-facing wording.
+- `chart_readings` and `claims` should cite what the chart means, not just which
+  column changed.
+
+## Label-Like And Probe-Derived Signals
+
+Signals such as `generated_probe1_false_detection`, `probe1_false_detection`,
+or anything that perfectly re-measures the FAIL label are sanity checks. Treat
+them as measurement checks, never as root causes.
+
+Use labels like:
+
+- `Sanity check: probe false-detection flag`
+- `Probe says object is present`
+- `Attention focus share`
+- `Maximum relative attention`
+- `Mean relative attention`
+
+Do not lead a report with a label-reconstructing signal even when it has the largest
+effect size. Mention it as a sanity check, then rank non-leaky explanatory
+signals first.
+
+## Overall Result Shape
+
+The final answer should be claim-first:
+
+1. State the supported non-leaky finding in plain language.
+2. Mention label-reconstructing signals only as demoted sanity checks.
+3. Link each claim to evidence: confirmed signal, chart, or downstream test.
+4. Say what not to infer: association is not causality unless intervention tests
+   support it.

evalvitals/agent_assets/skills/nature-figure/LICENSE

@@ -0,0 +1,201 @@
+                                 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.