bootproof 0.1.0

package/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 2026 Bootproof contributors
+
+   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/README.md

@@ -0,0 +1,265 @@
+# BootProof
+
+> **The honest Run Button for repos — with proof, not vibes.**
+
+**Human diagnosis. Machine proof. One engine.**
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/rossbuckley1990-hash/bootproof/main/assets/bootproof_viral_demo.gif" alt="BootProof demo" width="900">
+</p>
+
+BootProof inspects a local repository, builds an evidence-based run plan, executes only what it can justify, observes HTTP health, and writes a signed attestation for success or failure.
+
+It does not turn every repository green. That would defeat the point.
+
+```text
+No proof, no green check.
+```
+
+## One engine. Two interfaces.
+
+Humans run:
+
+```bash
+bootproof up .
+```
+
+They get a diagnosis and a runbook.
+
+Machines run:
+
+```bash
+bootproof up . --ci --json
+```
+
+They get a signed verdict and a deterministic exit code.
+
+The same engine powers both.
+
+## What It Tells Humans
+
+A failed run is still useful:
+
+```text
+NOT VERIFIED — package_manager_version_mismatch
+What happened: The repository requires pnpm 10.24.0, but this environment has pnpm 9.15.4.
+Why BootProof refused: The dependency install cannot be trusted with the wrong package manager version.
+Safe next step: Run corepack enable && corepack prepare pnpm@10.24.0 --activate, then rerun BootProof.
+Evidence: .bootproof/attestation.json
+```
+
+BootProof distinguishes diagnosis from proof. Detecting Python, Flask, React, Celery, Go, or a monorepo does not mean BootProof claims full orchestration support for that stack.
+
+## What It Gives Machines
+
+`--json` emits exactly one `bootproof/result/v1` object to stdout:
+
+```json
+{
+  "schema": "bootproof/result/v1",
+  "booted": false,
+  "healthVerified": false,
+  "failureClass": "dependency_install_skipped",
+  "attestationPath": ".bootproof/attestation.json",
+  "inference": {},
+  "plan": {},
+  "observed": []
+}
+```
+
+`--ci` disables colour and interactive output. Exit codes are deterministic:
+
+- `0`: `booted === true` and `healthVerified === true`
+- `1`: every refusal, ambiguity, install failure, service failure, app failure, or health failure
+
+## Quick Start
+
+Run against a local repository:
+
+```bash
+cd /path/to/repository
+npx bootproof up .
+```
+
+Host execution can be selected explicitly:
+
+```bash
+npx bootproof up . --provider local --unsafe-local
+```
+
+Run dependency installation only when intended:
+
+```bash
+npx bootproof up . --install
+```
+
+Explain and verify the signed result:
+
+```bash
+npx bootproof explain .bootproof/attestation.json
+npx bootproof verify .bootproof/attestation.json
+```
+
+Run against a public GitHub repository:
+
+```bash
+npx bootproof up https://github.com/user/repo
+```
+
+BootProof clones credential-free HTTPS GitHub URLs into `.bootproof/remotes/` and retains the clone so its evidence and any generated files continue to exist. It inspects the clone but refuses to execute remote code until host execution is explicitly acknowledged:
+
+```bash
+npx bootproof up https://github.com/user/repo --provider local --unsafe-local
+```
+
+Review the inferred commands before using that acknowledgement. Add `--install` only when you also intend to run dependency installation and its lifecycle scripts. Remote `--dry-run` is refused before cloning because dry runs promise to write nothing.
+
+Contributors working from this source repository can use `npm ci`, `npm run build`, and `npm link`. Those steps are not required for npm users.
+
+## Honesty Contract
+
+BootProof is constrained on purpose:
+
+- no verified boot without an observed health signal
+- no success rendering for skipped steps
+- no invented secrets
+- no writes to `.env`, `.env.local`, `.env.development`, or `.env.production`
+- no silent project patching
+- no guessed workspace when the repository is ambiguous
+- no claim that generated scaffolding exists unless it was written
+- signed failed attestations for refusals and execution failures
+- raw local evidence preserved in the attestation
+- no telemetry or hidden evidence upload
+
+See [docs/HONESTY_CONTRACT.md](docs/HONESTY_CONTRACT.md).
+
+## Current Capabilities
+
+BootProof currently provides:
+
+- Node package-manager and start-command inference
+- Python/Flask and Go/Node hybrid detection
+- monorepo candidate ranking
+- Docker service dependency detection and scaffolding
+- localhost health-candidate discovery from repository evidence and app logs
+- classified failures
+- signed Ed25519 attestations
+- strict JSON and fail-closed CI output
+- redacted registry-entry export
+
+Detection is broader than orchestration. For example:
+
+- Superset-like Python/Flask/React/Celery repos are detected, then honestly refused with `python_flask_setup_required`.
+- Grafana-like Go/Node hybrids are detected without pretending a frontend watcher is the whole application.
+- Parallel monorepo root commands are refused until a specific workspace is selected.
+
+## Files Written
+
+Depending on the observed plan, BootProof may write:
+
+```text
+.bootproof/attestation.json
+.bootproof/registry-entry.json
+docker-compose.bootproof.yml
+.env.bootproof.example
+```
+
+`registry-entry.json` is written only by `bootproof attest export`.
+
+Docker and env guidance files are listed in proof only when BootProof actually generated them.
+
+Protected application env files remain untouched.
+
+## Attestation Trust
+
+Current attestations contain:
+
+```json
+{
+  "trust": {
+    "level": "local_developer_signed",
+    "signer": "local_ed25519",
+    "oidc": null
+  }
+}
+```
+
+Local attestations are useful evidence. CI/OIDC attestations are stronger supply-chain proof. BootProof does not pretend local laptop proof is enterprise CI proof.
+
+The future `ci_oidc_signed` level is reserved but is not emitted today.
+
+## Failure Taxonomy
+
+Examples include:
+
+- `not_an_application`
+- `workspace_ambiguous`
+- `dependency_install_skipped`
+- `package_manager_version_mismatch`
+- `python_flask_setup_required`
+- `service_port_allocated`
+- `postgres_auth_env_missing`
+- `health_http_error`
+- `health_check_timeout`
+- `unknown_failure`
+
+Unknown failures remain unknown, with evidence preserved for the next detector.
+
+See [docs/FAILURE_TAXONOMY.md](docs/FAILURE_TAXONOMY.md).
+
+## Real Repository Evidence
+
+BootProof records both useful successes and useful failures. The evidence ledger does not relabel failure as support.
+
+See [docs/REAL_REPO_EVIDENCE.md](docs/REAL_REPO_EVIDENCE.md).
+
+## CI And Registry
+
+BootProof does not upload attestations. A project can deliberately commit `.bootproof/` or export a redacted registry entry.
+
+The Git-native registry and OIDC-backed trust model are designs in progress, not deployed services.
+
+- [docs/CI_ACTION.md](docs/CI_ACTION.md)
+- [docs/REGISTRY.md](docs/REGISTRY.md)
+
+## Release Packaging
+
+The npm package contains the compiled CLI, license, README, and docs. `dist/` is required at runtime, generated by `npm run build` during `prepack`, and intentionally not committed.
+
+Run `npm run pack:check` to pack BootProof, install the tarball in an isolated temporary directory, and exercise the installed CLI. See [docs/RELEASE_CHECKLIST.md](docs/RELEASE_CHECKLIST.md).
+
+## Release Hygiene
+
+`node_modules/`, `.DS_Store`, and generated `dist/` are ignored and not committed.
+
+`dist/` is generated by `npm run build`. It is included in the npm package because `dist/cli.js` is the executable, and `npm pack`/publish runs the `prepack` build.
+
+Repository metadata points to:
+
+```text
+https://github.com/rossbuckley1990-hash/bootproof
+```
+
+## What BootProof Is Not
+
+BootProof is not a deployment platform, a general CI replacement, or a magic environment fixer.
+
+It is the honest Run Button for repos. It runs what it can, refuses what it cannot prove, signs both success and failure, and gives humans and machines the same evidence.
+
+## Status
+
+BootProof is early alpha.
+
+Near-term work includes:
+
+- additional remote source providers beyond public HTTPS GitHub repositories
+- stronger multi-service orchestration
+- broader Python and Go execution support
+- CI/OIDC-backed signing
+- proof-linked badges and a verified public index
+
+Unsupported paths should fail clearly, not magically.
+
+## License
+
+Apache-2.0

package/dist/cli.d.ts

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+export {};