@filelayer/core 0.3.0

package/CHANGELOG.md

@@ -0,0 +1,338 @@
+# Changelog
+
+All notable changes to `@filelayer/core`.
+
+Format loosely follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+Versioning is pre-1.0 and is explained in [`MIGRATIONS.md`](MIGRATIONS.md) §1.
+
+## A note on honesty, before the entries
+
+**No version of this package has been published to npm.** The versions below are
+real, dated development milestones in this repository, not registry releases. We
+are writing them up as a changelog rather than starting the history at the first
+publish because a consumer deciding whether to depend on a `0.x` library is
+entitled to know what has already moved underneath it, and because most of the
+entries are security defects we found in our own code.
+
+They are described the way we found them, including the ones that were
+embarrassing. A changelog that only records features is a marketing document.
+
+`0.3.0` is the version prepared for the first publish.
+
+---
+
+## [Unreleased] — group grant subjects (RFC-001)
+
+Breaking schema change, additive API. Migration: `MIGRATIONS.md` Entry 2.
+
+### Fixed
+
+- **A byte range could be sent as `HTTP 200`, which is silent data corruption.**
+  `readStream()` and `redeemStream()` accept a byte range and attach
+  `Content-Range` when the store serves one, but `sendNodeStream()` and
+  `toStreamResponse()` both hardcoded `200`. Anyone following the documented
+  advice to wire the `Range` request header themselves emitted a **truncated
+  body under a 200** — which every HTTP client treats as the complete
+  representation, so it is cached, hashed and handed on with no error anywhere.
+  Both writers now derive the status from the delivery: `206` with
+  `Content-Range` when a range was served, `200` otherwise. There is deliberately
+  no status parameter — there is no value a caller could supply that the writer
+  does not already know, and every value they could supply by mistake is wrong.
+  Covered by four tests in `test/delivery.test.ts`.
+
+### Added
+
+- **`grant_subject := actor | org | role | link | anonymous`.** A grant's
+  subject is a principal set, and `org` / `role` are the missing middle between
+  "one person" and "everyone". Two new columns on `file_grant`,
+  `subject_org_id` and `subject_min_role`.
+  - **Resolution is a join, never a materialization.** Adding or removing an org
+    member changes access on the very next request, with no recomputation and no
+    write to any grant row. Asserted by fingerprinting every `file_grant` row
+    across a join, a leave and a role change.
+  - **Cross-org grants inside a project are the point** ("the company that
+    posted this job may read this CV"). Cross-**project** ones are
+    unrepresentable, by composite foreign key.
+  - No custom groups, no nested orgs, no configurable inheritance, no deny
+    rules. `subject_min_role` is only a threshold over the existing
+    `viewer | member | admin | owner` enum.
+- **I6 — subject breadth may not be amplified by delegation.** An issuer whose
+  authority is role-derived may mint any subject type; an issuer whose authority
+  is grant-derived may mint only `actor` or `link`. Enforced in
+  `authorizeShare()` (reason `subject_breadth_amplification`, `403`, audited)
+  **and** in the `file_grant_attenuate()` trigger (`grant_subject_amplification`),
+  so it binds a caller issuing raw SQL. The trigger now also fires on the subject
+  columns, so a delegated grant cannot be widened by a later `UPDATE`.
+- `AuthzPath` gains `grant:org` and `grant:role`. Group allows carry `viaOrgId`,
+  `viaMinRole` and `viaRole` in the audit context, so a compliance auditor can
+  see which membership conferred access.
+- `shares.create(fileId, { as, withOrg, minRole })` on the tiered API.
+  `withOrg` does **not** auto-provision a tenant: an unknown org is `404`.
+
+### Changed
+
+- `grant_scope_is_live()` takes a fourth argument and gains one term: a grant is
+  live only while its **subject org** is live (I2). Deleting an org now kills the
+  grants held by its members, as it already killed the grants on its files.
+- `file.visibility = 'org'` is **retained**, and is now describable as an
+  implicit org grant.
+
+### Fixed
+
+- **`getActorGrants` had no `ORDER BY`, and the delegation parent depended on
+  it.** `resolveStanding` attributes an allow to the first returned grant
+  carrying the requested capability, and on the share path that grant becomes
+  the child's `parent_grant_id` — the ceiling the attenuation trigger measures
+  against. With no ordering, Postgres returned heap order, which is undefined
+  and moves with page layout, `VACUUM` and row width. A principal holding
+  several grants on one file could therefore have `share()` succeed or fail
+  depending on physical storage. Fail-closed, never a disclosure, but not a
+  semantics anyone could document. Now ordered oldest-first. Found while adding
+  the columns above, which was enough to flip it.
+
+### Known, recorded rather than hidden
+
+- `authorizeShare` computes the issuer's held capabilities as the **union** over
+  every source, while `parent_grant_id` is a **single** grant. A principal
+  holding several grants on one file can therefore be approved for a capability
+  set that no one ancestor covers, and the attenuation trigger then refuses the
+  insert. The outcome is a `403` rather than a disclosure, so P4 is intact; what
+  is wrong is that a legitimate delegation can be refused. Closing it means
+  changing the delegation model (pick a covering parent, or mint one child per
+  contributing ancestor) and was out of scope for RFC-001.
+
+---
+
+## [0.3.0] — 2026-09-05
+
+The release that makes the package installable, and the one that closes the
+last cross-tenant defect.
+
+### Added
+
+- **Compiled output.** The package now ships `dist/` (JavaScript plus `.d.ts`)
+  and its `exports` point at it. Previously `exports` pointed at `src/index.ts`,
+  which is not importable from an install: Node refuses to strip types from
+  files under `node_modules`
+  (`ERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING`). The package was installable
+  and unusable.
+- **The TypeScript source and the full test suite ship in the tarball**, so
+  every claim in the README is inspectable from what you installed. They cannot
+  be *run* from `node_modules` for the reason above; clone the repository.
+- `SEMANTICS.md`, `MIGRATIONS.md`, `CHANGELOG.md` and `LICENSE` are in the
+  tarball.
+- **A transaction abstraction.** `withTransaction()`, `Tx`, and `Queryable`
+  gaining an optional `withTransaction` hook. `pg.Pool` is now used through
+  `connect()`, so a transaction stays on one connection instead of scattering
+  across the pool.
+- **Streaming.** `upload()` accepts a `ReadableStream`; the storage interface
+  gained `stream()`, `head()` and an optional `list()`; delivery can stream
+  rather than buffer. `toStreamResponse()` returns a streaming WHATWG
+  `Response`.
+- **Byte-range reads** at the storage and delivery API level. The shipped HTTP
+  route helpers still do not parse the `Range` request header and never return
+  `206`.
+- **Redirect delivery** — an opt-in mode that hands out a short-lived presigned
+  URL instead of proxying bytes, for deployments that need a CDN. Off by
+  default; restricted to anonymous grants unless widened; requires passing a
+  verbatim acknowledgement constant, because it trades a bounded revocation
+  window for the byte path and that trade must be made deliberately.
+- `collectStorageOrphans()` — collection for objects written by an upload whose
+  metadata never committed.
+
+### Fixed
+
+- **Cross-project identity collision (HIGH).** `org.external_id` and
+  `actor.external_id` were globally unique. In any deployment where more than
+  one application shares a database, application B calling `put({ org: 'acme'
+  })` did not get an error — it got application A's org id, and the identity
+  resolver then added B's user to A's tenant as a `member`. Same shape for
+  actors, so `as: 'alice'` resolved across the boundary too. A complete
+  cross-tenant compromise reachable from the most ergonomic entry point in the
+  library. Fixed by introducing a **project** scope above the tenant and making
+  every access-bearing table carry `project_id` under a composite foreign key,
+  so a cross-project row is unrepresentable rather than merely unlikely.
+  **Breaking schema change — see [`MIGRATIONS.md`](MIGRATIONS.md) entry 1.**
+- **A soft-deleted org stopped conferring membership but did not kill
+  outstanding grants.** Deleting a tenant removed the owner's access and left a
+  contractor's share link serving bytes. Nobody chose that; it was an emergent
+  asymmetry between two store methods, found because the set query and the point
+  check disagreed. Grant liveness is now a predicate over the whole scope — the
+  file, its org, that org's project, the subject actor and the issuing actor —
+  evaluated on every request, with no cascading write, so a restore revives
+  exactly what the delete killed.
+- **`maxDownloads` was charged only on the share-link path.** An actor grant
+  carrying `maxDownloads: 3` permitted unlimited direct authenticated reads,
+  because nothing on that path touched the counter. The field meant "link
+  redemptions" on one path and nothing at all on the other, while being named,
+  documented and billed as a download cap. A download is now charged whenever
+  bytes leave through a grant, by any principal, on any path. Authority derived
+  from an org role is not charged (a role is not a metered credential) and
+  metadata reads are not charged (no bytes leave).
+- **The audit hash chain could fork under concurrent writers.** It was built
+  with a `SELECT` of the last hash followed by an `INSERT`, from application
+  code, in two statements — atomic only under a single serialized writer. It is
+  now one call to `audit_append()`, which takes `pg_advisory_xact_lock` on the
+  chain, reads the predecessor and inserts, inside one statement. The library
+  runs that in the same transaction as the mutation it describes, so the lock
+  covers both. Caveat stated plainly: the suite runs on PGlite, which has one
+  backend, so the test proves the lock is taken on the write path — the
+  multi-process argument rests on Postgres advisory-lock semantics.
+- **The audit write was not in the same transaction as the thing it audited.**
+  `put()` performed five independent statements; a failure after the second left
+  a file with no audit record. For a product whose selling point is a
+  tamper-evident trail, an intact chain that simply does not mention what
+  happened is a hole in the premise.
+- **`file.storage_provider` was written as the literal `'memory'` on every
+  insert**, regardless of the configured adapter, so a production deployment
+  recorded every object as living in an in-process map. It participates in a
+  unique index with the key and is therefore half of an object's identity, not a
+  label.
+- **Unauthenticated audit-chain growth is now bounded.** A caller probing org
+  ids can only reach a tenant chain inside a project they are already
+  authenticated for; probes at every other id land on the system chain. Still
+  requires rate limiting at ingest — denials are audited by design and that is
+  not negotiable — but the reach went from "any internet caller, any tenant" to
+  "an authenticated customer, their own tenant".
+
+### Changed
+
+- **Breaking:** the schema requires a `project` row. A default project is
+  inserted by `schema.sql`, so a single-application deployment needs no project
+  vocabulary.
+- **Breaking:** `engines.node` is `>=22.18` and enforced.
+- **Licensed under Apache-2.0.** `license` was `UNLICENSED` and `LICENSE` was an
+  explicit placeholder granting no rights; both are resolved before this version
+  is published. `LICENSE` is now the verbatim Apache License 2.0 and ships in
+  the tarball alongside a `NOTICE` file, so the grant travels with the package
+  rather than only with the repository. See
+  [LICENSE](https://github.com/filelayer/filelayer/blob/main/LICENSE) and
+  [NOTICE](https://github.com/filelayer/filelayer/blob/main/NOTICE).
+- Scratch and diagnostic scripts moved out of the package root into `dev/` and
+  are excluded from the tarball. The `package.json` scripts that referenced them
+  moved to the repository root.
+- Documentation was swept of internal review vocabulary, and a CI check now
+  fails the build if it comes back.
+
+### Known limitations at this version
+
+Listed in the README, and repeated here because a changelog that only records
+wins is not one: no `Range` responses from the shipped routes; no direct
+browser-to-storage upload; org admins can read `private` files; identifiers are
+per-project, not per-org; the S3/R2 adapter has never run against live
+credentials; orphan collection and ingest rate limiting are jobs you schedule.
+
+---
+
+## [0.2.0] — 2026-09-05
+
+The security rebuild. Twelve defects found by an independent review of the
+authorization core plus five found while fixing them. This is the release where
+the delivery layer stopped being the developer's problem.
+
+### Fixed — authorization
+
+- **A delegated grant outlived the grant that created it (HIGH).** Revoking a
+  grant left everything delegated from it alive, which meant the central claim —
+  a URL never outlives its permission — was true only for directly-issued
+  grants. Liveness is now evaluated over the whole ancestor chain, in the
+  schema, so revocation is transitive at any depth with no cascading write.
+- **Capability amplification through `share` (HIGH).** A holder of `read` could
+  mint a grant carrying `delete`. Attenuation is now enforced by the
+  authorization engine *and* again by a `BEFORE INSERT` trigger, so it binds a
+  migration or a `psql` session as well as an API call.
+- **Membership management had no authorization and no audit (HIGH).** Anyone who
+  could reach the method could change anyone's role. Now: you may not grant a
+  role above your own, may not modify anyone who outranks you, may not remove
+  the last owner, and every attempt — allowed or denied — is audited.
+- **Holding `share` conferred revoke over every grant on the file.** A
+  contractor given the ability to share could revoke the owner's grants.
+  Narrowed to the grants in your own delegation subtree.
+- **A `link` grant could carry `delete`.** A leaked share link could destroy the
+  file it pointed at. Share links are read-only by database constraint now.
+
+### Fixed — the audit trail
+
+- **Enumeration left no trace (HIGH).** Decisions that could not be attributed
+  to a tenant — a probe against a file id that does not exist, a sweep against
+  link secrets — were dropped rather than recorded, which made exactly the
+  reconnaissance the log exists to catch invisible. They now go to a system
+  chain (`org_id IS NULL`) that no tenant can read.
+- **An exhausted download cap was not audited.** "Why did my link stop working"
+  was unanswerable from the log.
+- **The hash chain did not cover the forensic fields.** The digest covered seven
+  columns; `reason`, `grant_id`, `ip`, `user_agent` and `context` — the fields an
+  incident responder relies on and an attacker would rewrite — were outside the
+  commitment, which made the chain decorative for the questions that matter. The
+  digest now covers every forensically relevant column, encoded as canonical
+  JSON rather than concatenated, because concatenation lets a forger shift field
+  boundaries.
+- **A well-formed but unregistered actor id crashed the audit write (HIGH).**
+  `audit_event.actor_id` carried a foreign key to `actor`, so a caller
+  presenting an unknown-but-valid id could not be audited at all: the insert
+  raised, the exception propagated out of `authorize()`, the denial was never
+  recorded, and the caller got a 500 where a real stranger gets a 404 — an
+  actor-existence oracle and a silent hole in the denial log, at once. The
+  foreign key is gone; recording identifiers that do not exist is the audit
+  log's job.
+
+### Fixed — the error surface and delivery
+
+- **The error surface was an existence oracle.** Denials are now uniformly 404
+  and the evaluation order that makes that true is itself a security property.
+- **`Content-Disposition` filenames were interpolated, not encoded** — response
+  splitting through an uploaded filename. On one comparison implementation the
+  same bug turns every share download of an affected document into a permanent
+  500.
+- **`upload()` took a bare actor id (HIGH)**, so ownership was forgeable from a
+  request body. It takes an authorized principal now.
+- **Byte delivery was the developer's problem (HIGH).** `read()` returned a
+  `Uint8Array` and the application chose `Content-Type`,
+  `Content-Disposition`, `X-Content-Type-Options` and `Cache-Control` — three
+  security-sensitive decisions handed back to the developer by a library
+  claiming to have removed them, and the example got them wrong. `get()` now
+  returns `headers`, computed from the file record, with no option to disable
+  them.
+- **A credential could be passed in a share-link query string.** Refused with
+  `400 credential_in_query`, before any work, without consuming a download.
+  Query strings end up in access logs, proxy logs and browser history.
+
+### Added
+
+- **An authorized listing primitive (HIGH — its absence was the defect).** There
+  was no way to ask "which files may this caller see?", so building a listing
+  screen meant hand-rolling the org filter, the visibility rule, the owner
+  check, the role check and a union over the grant table in application SQL.
+  `listFiles()` answers it in one query and one audit event, with no filter
+  parameter to forget. `test/listing.test.ts` asserts set equality against
+  `authorize()` over a randomized corpus on every capability, every run — a set
+  query that is too wide *or* too narrow fails the build.
+- **File-level `visibility`.** Every member of an org could previously read
+  every file in it. Files are now `private` by default — owner and org admins
+  only — and org-wide visibility is something the creator asks for.
+
+### Known and reported, not fixed at this version
+
+- `authorize()` is file-scoped, so creation authorization sits outside it.
+  Narrowed to a single `authorizeOrg('create_file')` call, not eliminated.
+- Unauthenticated callers can append denial events to a known tenant's audit
+  chain. Bounded in 0.3.0.
+- `maxDownloads` charged only on redemption. Fixed in 0.3.0.
+- The audit chain could fork under concurrent writers. Fixed in 0.3.0.
+- A soft-deleted org left outstanding grants alive. Fixed in 0.3.0.
+
+---
+
+## [0.1.0] — 2026-09-04
+
+Initial implementation.
+
+- The data model: projects had not been invented yet, so orgs, actors, files,
+  memberships, grants and a hash-chained audit log, with tenant isolation
+  enforced by composite foreign key rather than by `WHERE` clause.
+- The authorization engine: one decision core, reached from a point check.
+- The tiered facade — `files`, `orgs`, `shares` — over it.
+- `MemoryStorage`, and an S3/R2 adapter that had not been run against anything.
+- Share links with expiry, password and download cap.
+
+Every defect in the 0.2.0 list above was present in this version.

package/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.