the big lift 🏗️

Author: Ethan-Arrowood

.github/workflows/integration-test.yml

@@ -0,0 +1,75 @@
+name: Integration Test
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_dispatch:
+    inputs:
+      node-version:
+        description: 'Node.js version'
+        required: true
+        type: choice
+        default: 'all'
+        options:
+          - 'all'
+          - '20'
+          - '22'
+          - '24'
+
+jobs:
+  integration-test:
+    name: Integration Test (Node.js v${{ matrix.node-version }})
+    runs-on: ubuntu-latest
+
+    strategy:
+      fail-fast: false
+      matrix:
+        node-version: ${{ (github.event.inputs.node-version == 'all' || github.event.inputs.node-version == '') && fromJSON('[20, 22, 24]') || fromJSON(format('[{0}]', github.event.inputs.node-version)) }}
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v4
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Build
+        run: npm run build || true # we currently have type errors so just ignore that
+
+      - name: Setup Harper
+        env:
+          DEFAULTS_MODE: 'dev'
+          HDB_ADMIN_USERNAME: 'admin'
+          HDB_ADMIN_PASSWORD: 'password'
+          ROOTPATH: '/tmp/hdb'
+          OPERATIONSAPI_NETWORK_PORT: 9925
+          LOGGING_LEVEL: 'debug'
+          LOGGING_STDSTREAMS: true
+          THREADS_COUNT: 1
+          THREADS_DEBUG: false
+          NODE_HOSTNAME: 'localhost'
+        run: node --enable-source-maps ./dist/bin/harperdb.js install
+
+      - name: Run tests
+        env:
+          HDB_ADMIN_USERNAME: 'admin'
+          HDB_ADMIN_PASSWORD: 'password'
+        run: |
+          node --enable-source-maps ./dist/bin/harperdb.js start
+          sleep 10
+          npm run test:integration
+
+      - name: Upload HarperDB logs
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: harper-logs-node-${{ matrix.node-version }}
+          path: /tmp/hdb/log/hdb.log
+          retention-days: 7

.gitignore

@@ -1,3 +1,31 @@
+## New GitIgnore Rules
+## Keeping old ones for now so we don't accidentally start tracking something we were previously ignoring
+
+# OS Files
+.DS_Store
+
+# IDE Files
+.vscode/
+.idea/
+
+# Dependencies
 node_modules/
 
-.DS_Store
+# Test Outputs
+coverage
+*.lcov
+.nyc_output/
+
+# TypeScript
+*.tsbuildinfo
+
+# Build Output
+dist/
+
+# Environment Variables
+.env
+.env.*
+!.env.example
+
+# something is generating this file :shrug:
+integration-test.json

CODE_OF_CONDUCT.md

@@ -0,0 +1,90 @@
+
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
+
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, **send an email to moderation@harperdb.io with the subject "COC Violation Report" and all relevant details (including screenshots and timestamps) in the email body.**
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+
+## Addressing and Repairing Harm
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning from the Community Moderators.
+   3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
+
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).
+

CONTRIBUTING.md

@@ -0,0 +1,26 @@
+# Contributing to Harper
+
+> [!NOTE]
+> Harper open source core is still under active development.
+>
+> The source code in this repository was extracted directly from our old, closed-source codebase.
+>
+> Stay tuned to this repo and our public channels (such as our [Discord](https://discord.gg/VzZuaw3Xay) community) for updates as we continue to develop the future of open source Harper.
+
+Contributors are encouraged to communicate with maintainers in issues or other channels (such as our community [Discord](https://discord.gg/VzZuaw3Xay)) before submitting changes.
+
+## Getting Started
+
+Install dependencies using `npm install`
+
+Build the project using `npm run build` or `npm run build:watch` to automatically rebuild on file changes.
+
+Run tests using `npm run test:integration`. Make sure to read the [integration test instructions](./test/integrationTests/README.md) for setup.
+
+## Repository Structure
+
+Most of the content within this repo is source files. The exceptions are `static` and `test` directories, and various configuration files (such as `eslint.config.mjs`, `prettier.config.mjs`, and `tsconfig.json`).
+
+## Code of Conduct
+
+Harper has a [Code of Conduct](./CODE_OF_CONDUCT.md) that all contributors are expected to follow.

README.md

@@ -1,3 +1,38 @@
 # Harper
 
-https://harpersystems.dev
+> [!NOTE]
+> Harper open source core is still under active development.
+>
+> The source code in this repository was extracted directly from our old, closed-source codebase.
+>
+> Stay tuned to this repo and our public channels (such as our [Discord](https://discord.gg/VzZuaw3Xay) community) for updates as we continue to develop the future of open source Harper.
+
+## Getting Started
+
+Check out our [Getting Started Guide](https://docs.harperdb.io/docs/getting-started) to learn how to install and use Harper.
+
+## What is HarperDB?
+
+HarperDB is our previous name. Earlier in 2025, [we rebranded](https://www.harper.fast/announcements/harperdb-proclaims-new-era-for-web-performance-with-corporate-rebrand) to just "Harper" to reflect our evolution from a database to a full performance platform. The core technology remains the same, but we've expanded our vision to encompass more than just database functionality. Since this repo was created from the existing Harper codebase, you may still see references to the old name "HarperDB" in certain places.
+
+## Contributing to Harper
+
+Harper's open source core accepts contributions from the community! Please read our guidelines before contributing.
+
+Open an issue if you find a bug, or reach out on our [Discord](https://discord.gg/VzZuaw3Xay) if you have questions or want to discuss ideas.
+
+For more information on how to contribute, please see our:
+
+- [Contributing Guide](./CONTRIBUTING.md)
+- [Code of Conduct](./CODE_OF_CONDUCT.md)
+- [Support](./SUPPORT.md)
+
+## Security
+
+Please review our [Security Policy](./SECURITY.md) for reporting vulnerabilities.
+
+Please always disclose vulnerabilities privately to `security@harperdb.io` before making them public.
+
+## License
+
+Harper is available under the Apache-2.0 License. See the [LICENSE](LICENSE) for the full license text or the [License FAQ]() for more information.

SECURITY.md

@@ -0,0 +1,18 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+We take security vulnerabilities seriously and appreciate your efforts to responsibly disclose your findings.
+
+If you discover a security vulnerability, please email us at **security@harperdb.io** with the following information:
+
+- A description of the vulnerability
+- Steps to reproduce the issue
+- Potential impact
+- Any suggested fixes (if available)
+
+We will acknowledge receipt of your report and work with you to understand and resolve the issue promptly.
+
+**Please do not publicly disclose the vulnerability until we have had a chance to address it.**
+
+Thank you for helping keep Harper and our community safe.

SUPPORT.md

@@ -0,0 +1,26 @@
+# Support
+
+## Bug Reports
+
+If you encounter a bug, please file an issue directly in the respective repository where the issue occurs.
+
+## Community Help
+
+For general questions, help requests, and community discussions, please join our Discord community:
+
+**https://discord.gg/VzZuaw3Xay**
+
+## Code of Conduct Violations
+
+If you experience or witness behavior that violates our Code of Conduct, please:
+
+1. Review our [Code of Conduct](CODE_OF_CONDUCT.md)
+2. Email **moderation@harperdb.io** with details of the incident
+
+## Harper Customers
+
+If you are a HarperDB customer, you can reach our support team directly at **support@harperdb.io**.
+
+## Other Inquiries
+
+For any other open source-related concerns or questions, please contact **opensource@harperdb.io**.

bin/BinObjects.js

@@ -0,0 +1,17 @@
+'use strict';
+
+/**
+ * This is meant as a central place to defined POJOs used by functions in the /bin/ directory.
+ */
+
+class HdbInfoInsertObject {
+	constructor(id, dataVersionNum, hdbVersionNum) {
+		this.info_id = id;
+		this.data_version_num = dataVersionNum;
+		this.hdb_version_num = hdbVersionNum;
+	}
+}
+
+module.exports = {
+	HdbInfoInsertObject,
+};