@sap/cds-dk 9.9.3 → 10.0.4

package/node_modules/hdb/.claude/skills/hdb-commit-msg/SKILL.md

@@ -0,0 +1,132 @@
+---
+name: hdb-commit-msg
+description: Use when creating a new commit, making a commit, committing changes, or writing a commit message in node-hdb.
+---
+
+# hdb-commit-msg
+
+Generates a well-formatted git commit message for node-hdb following project conventions. Always confirms the message with the user before committing.
+
+## When to Use This Skill
+
+- User asks to make a new commit or commit changes
+- User asks to write or generate a commit message
+- User says "let's commit", "I want to commit", "commit this", or similar
+- User asks to amend a commit or update a commit message
+
+## Workflow
+
+1. Run `git status` to check staged and unstaged changes
+2. **Determine what to commit:**
+   - **Staged files exist:** use them as-is
+   - **No staged files, user specified files explicitly:** stage those files with `git add`
+   - **No staged files, user described the change:** infer relevant files from the description and `git status`, show them, and ask — "I'll stage these files: `[list]`. Does that look right?" — wait for confirmation, then stage
+   - **No staged files, no files or description mentioned:** stage all changed files with `git add -A`
+3. Run `git diff --staged` to analyze the staged changes
+4. Infer the commit type from the diff (see [Types](#types) below)
+5. Use no scope by default unless the user specifies one
+6. Ask: "Does this commit relate to a public issue? If so, what's the issue number?"
+7. Draft the commit message (header + body)
+8. Show the full message, then ask:
+
+   **"Does this commit message look good?"**
+   1. Yes, commit
+   2. Suggest changes
+
+9. On option 1, commit using a heredoc to preserve formatting:
+
+   ```bash
+   git commit -m "$(cat <<'EOF'
+   [TYPE](#issue)(scope) <summary description>
+
+   Relates to issue [#N](https://github.com/SAP/node-hdb/issues/N)
+
+   - <change 1>
+   - <change 2>
+   EOF
+   )"
+   ```
+   (Omit `(#issue)` and the `Relate to` line together if no public issue; omit `(scope)` if no scope.)
+
+   On option 2, apply the suggestion, revise, and re-ask
+
+## Commit Message Guidelines
+
+### Format
+
+```
+[header line]
+
+[body]
+```
+
+The header and body are separated by a blank line.
+
+#### Header Line
+
+```
+[TYPE](#issue)(scope) <summary description> 
+```
+
+- `(#issue)` and `(scope)` are both optional and independent
+- No period at end of header line
+- Brief and accurate; aim for under 72 characters but longer is fine if needed
+
+Examples from this repo:
+- `[FEATURE](stmt distr) add topology update records in reply`
+- `[INTERNAL] refactor vars to const/let in Connection.js`
+- `[FIX] fix failing compression unit-test after removing packet size checking`
+- `[FIX](#42) correct type mapping for DECIMAL columns` — with public issue
+- `[FIX](#42)(datatype) correct type mapping for DECIMAL columns` — with both
+
+#### Body
+
+Use bullet points to summarize notable changes — include what changed and why/benefit, skip trivial or self-explanatory edits.
+
+```
+- <change 1> [and why/benefit if non-obvious]
+- <change 2> [and why/benefit if non-obvious]
+```
+
+Example:
+
+```
+- add SystemInfo class to store and update connection topology information
+- remove redundant _connect() method from Connection as it's now handled by PhysicalConnection
+```
+
+### Types
+
+Mutually exclusive — one per commit:
+
+| Type | When to use |
+|------|-------------|
+| `FEATURE` | New feature visible to users or callers |
+| `FIX` | Bug fix |
+| `TEST` | Adding or updating tests only |
+| `DOC` | README.md changes only |
+| `INTERNAL` | Non-functional changes, refactoring, comments |
+| `RELEASE` | Version bumps, release assembly |
+| `INFRA` | Build or test infrastructure only |
+
+### Rules
+
+- Imperative mood throughout — use the base verb form for header and every body bullet (e.g., "add" not "added"/"adds", "remove" not "removed"/"removes")
+- No AI attribution footers (`Co-Authored-By: Claude`, `🤖 Generated with...`)
+
+## Interactive Prompts
+
+- **Scope:** No scope by default; only include if the user specifies one
+- **Public issue reference:** Ask the user if the commit relates to a public issue before drafting. Only applicable for `[FIX]` (bug label) and `[FEATURE]` (enhancement label) commits. If yes, include `(#issue)` in the header and a `Relates to` line as the first line of the body:
+
+  ```
+  [FIX](#42)(stmt distr) correct type mapping for DECIMAL columns
+
+  Relates to issue [#42](https://github.com/SAP/node-hdb/issues/42)
+
+  - fix DECIMAL type mapping to return correct JS number
+  ```
+
+  `(#issue)` and `(scope)` are both optional and independent — include neither, either, or both as appropriate.
+- **Breaking changes:** If the diff suggests a breaking API/behavior change, ask the user to confirm, then include `(BREAKING CHANGE)` on its own line in the body
+- **Multi-area changes:** If changes span clearly unrelated areas, suggest splitting into multiple commits before proceeding

package/node_modules/hdb/.hyperspace/pull_request_bot.json

@@ -0,0 +1,26 @@
+{
+  "$schema": "https://devops-insights-pr-bot.cfapps.eu10-004.hana.ondemand.com/schema/pull_request_bot.json",
+  "features": {
+    "control_panel": true,
+    "summarize": {
+      "auto_generate_summary": false,
+      "auto_insert_summary": false,
+      "auto_run_on_draft_pr": false,
+      "use_custom_summarize_prompt": false,
+      "use_custom_summarize_output_template": false,
+      "excluded_paths": [],
+      "auto_exclude_authors": []
+    },
+    "review": {
+      "auto_generate_review": false,
+      "auto_run_on_draft_pr": false,
+      "use_custom_review_focus": false,
+      "excluded_paths": [],
+      "auto_exclude_authors": []
+    },
+    "pipeline_fix": {
+      "enable": true
+    }
+  },
+  "excluded_paths": ["package-lock.json"]
+}

package/node_modules/hdb/.jshintrc

@@ -0,0 +1,41 @@
+{
+  "node": true,
+  "asi": false,
+  "boss": false,
+  "eqnull": false,
+  "evil": false,
+  "expr": false,
+  "funcscope": false,
+  "smarttabs": true,
+  "shadow": false,
+  "sub": false,
+  "supernew": false,
+  "bitwise": true,
+  "camelcase": true,
+  "curly": true,
+  "eqeqeq": true,
+  "forin": true,
+  "immed": true,
+  "indent": 2,
+  "latedef": false,
+  "loopfunc": false,
+  "maxerr": 7,
+  "newcap": true,
+  "noarg": true,  
+  "nonew": true,
+  "plusplus": false,
+  "quotmark": "single",
+  "regexdash": false,
+  "undef": true,
+  "unused": true,
+  "strict": true,
+  "trailing": true,
+  "white": true,
+  "predef": [
+      "describe",
+      "it",
+      "before",
+      "after"
+  ]
+}
+

package/node_modules/hdb/.pipeline/config.yml

@@ -0,0 +1,21 @@
+general:
+  buildTool: 'npm'
+  productiveBranch: 'main'
+  vaultPath: 'piper/sap-project-hana-clients'
+  vaultBasePath: 'piper/sap-project-hana-clients'
+  vaultPipelineName: 'node-hdb'
+  vaultServerUrl: 'https://vault.tools.sap'
+  vaultNamespace: 'ies/hyperspace/pipelines'
+  nativeBuild: true
+stages:
+  Release:
+    sapDownloadArtifact: false
+  Post:
+    # Secret rotation handled by Hyperspace Portal, enabling it back might cause unintended behavior
+    vaultRotateSecretId: false
+steps:
+  sapCallStagingService:
+    url: 'https://staging.repositories.cloud.sap/stage/api'
+    profile: 'group-sap-hana-clients-project-default'
+  sapCumulusUpload:
+    pipelineId: '363d2eca-f232-4d6e-8e16-1ca82a395d87'

package/node_modules/hdb/.reuse/dep5

@@ -0,0 +1,28 @@
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: node-hdb
+Source: https://github.com/SAP/node-hdb
+Disclaimer: The code in this project may include calls to APIs (“API Calls”) of
+ SAP or third-party products or services developed outside of this project
+ (“External Products”).
+ “APIs” means application programming interfaces, as well as their respective
+ specifications and implementing code that allows software to communicate with
+ other software.
+ API Calls to External Products are not licensed under the open source license
+ that governs this project. The use of such API Calls and related External
+ Products are subject to applicable additional agreements with the relevant
+ provider of the External Products. In no event shall the open source license
+ that governs this project grant any rights in or to any External Products,or
+ alter, expand or supersede any terms of the applicable additional agreements.
+ If you have a valid license agreement with SAP for the use of a particular SAP
+ External Product, then you may make use of any API Calls included in this
+ project’s code for that SAP External Product, subject to the terms of such
+ license agreement. If you do not have a valid license agreement for the use of
+ a particular SAP External Product, then you may only make use of any API Calls
+ in this project for that SAP External Product for your internal, non-productive
+ and non-commercial test and evaluation of such API Calls. Nothing herein grants
+ you any rights to use or access any SAP External Product, or provide any third
+ parties the right to use of access any SAP External Product, through API Calls.
+
+Files: *
+Copyright: 2013-2021 SAP SE or an SAP affiliate company and node-hdb contributors
+License: Apache-2.0

package/node_modules/hdb/CLAUDE.md

@@ -0,0 +1,41 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+Pure JavaScript SAP HANA database client for Node.js (≥18).
+
+## Development Guidelines
+
+- **Backward compatibility**: This is a published npm package — any change visible to consumers must be backward compatible. This includes public method and callback signatures, emitted events, exported names, and existing behavior.
+- **Naming**: `_` prefix for private fields/methods (`_socket`, `_cleanup()`); no prefix for public ones.
+- **Variables**: Always `const`/`let`, never `var`. When modifying existing code, convert nearby `var` declarations too.
+- **Classes**: ES6 `class` for new classes; existing `util.inherits` classes stay as-is — only add new methods to them.
+
+## Architecture
+
+`Client` is the public API entry point. It delegates to `Connection`, the logical layer that owns the request queue, session state, and a `PhysicalConnectionSet`. `PhysicalConnection` handles the actual socket I/O: TCP connect, HDB handshake, compression, and packet framing.
+
+`ConnectionManager` is a connect-time utility that handles multi-host failover and MDC tenant routing; it is discarded once the connection is open.
+
+**Data Flow**: `Client` → `Connection` → `PhysicalConnection` → HANA server.
+
+**Protocol Wire Format**: `lib/protocol/common/` defines constants and enums. `lib/protocol/request/` and `lib/protocol/reply/` handle segment and part serialization. `lib/protocol/data/` contains per-part-kind read/write codecs.
+
+## Testing
+
+```bash
+# Run all tests (unit + acceptance)
+make test
+
+# Run unit tests only (no HANA server needed)
+make test-unit
+
+# Run acceptance tests only (requires HANA server)
+make test-acceptance
+```
+
+Acceptance tests require `test/db/config.json` (copy from `test/db/config.tpl.json` and fill in credentials). Without it, a local mock server starts automatically.
+
+Unit tests in `test/` cover individual modules (e.g. `lib.Connection.js`, `lib.ConnectionTopology.js`). Acceptance tests in `test/acceptance/` exercise a real HANA server. The mock server (`test/mock/server.js`) replays canned responses for auth + basic SQL operations. `test/TestUtil.js` provides topology test helpers (`TopologyTestUtils`).

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

package/node_modules/hdb/LICENSES/Apache-2.0.txt

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

package/node_modules/hdb/Makefile

@@ -0,0 +1,41 @@
+MOCHA          = ./node_modules/.bin/mocha
+MOCHA_REPORTER = spec
+
+C8             = ./node_modules/.bin/c8
+C8_REPORTERS   = --reporter=text --reporter=html --reporter=lcov
+
+test:
+	@NODE_ENV=test $(MOCHA) \
+		-R $(MOCHA_REPORTER) -b	--recursive
+
+test-unit:
+	@NODE_ENV=test $(MOCHA) \
+		-R $(MOCHA_REPORTER) -b
+
+test-acceptance:
+	@NODE_ENV=test $(MOCHA) \
+		-R $(MOCHA_REPORTER) -b	test/acceptance/*.js
+
+test-coverage:
+	@NODE_ENV=test $(C8) $(C8_REPORTERS) $(MOCHA) \
+		-R $(MOCHA_REPORTER) -b	--recursive
+
+test-unit-coverage:
+	@NODE_ENV=test $(C8) $(C8_REPORTERS) $(MOCHA) \
+		-R $(MOCHA_REPORTER) -b
+
+test-acceptance-coverage:
+	@NODE_ENV=test $(C8) $(C8_REPORTERS) $(MOCHA) \
+		-R $(MOCHA_REPORTER) -b	test/acceptance/*.js
+
+test-mock:
+	@HDB_MOCK=1 $(MAKE) -s test
+
+clean:
+	@rm -rf ./coverage \
+	@rm -f hdb.js
+
+chromify:
+	@browserify -r buffer -r ./lib:hdb -o ./hdb.js
+
+.PHONY: test test-unit test-acceptance test-coverage test-unit-coverage test-acceptance-coverage clean