Skip to content
Back to search

Aletheore

Evidence-grounded repository audit CLI - deterministic scanner, MCP server, live dashboard, and a GitHub Action that posts PR diffs.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Aletheore/Aletheore with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Aletheore/Aletheore'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/aletheore--aletheore/badge.svg)](/listings/aletheore--aletheore)

HTML

<a href="/listings/aletheore--aletheore"><img src="/api/listings/aletheore--aletheore/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 430 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <img src="assets/logo.png" alt="Aletheore" width="320">
  3. </p>
  4. <h3 align="center">Understand your code. Trace the impact of a change.</h3>
  5. <p align="center">
  6. Scan a repository into structured evidence, inspect its dependencies and ownership,
  7. and give coding agents and PR reviews concrete source context.
  8. </p>
  9. <p align="center">
  10. <a href="https://github.com/Aletheore/Aletheore/releases/latest"><img src="https://img.shields.io/github/v/release/Aletheore/Aletheore?label=release&amp;color=dd8034" alt="Latest GitHub release"></a>
  11. <a href="https://pypi.org/project/aletheore/"><img src="https://img.shields.io/pypi/v/aletheore?color=blue" alt="PyPI version"></a>
  12. <a href="https://pypi.org/project/aletheore/"><img src="https://img.shields.io/pypi/pyversions/aletheore" alt="Supported Python versions"></a>
  13. <a href="LICENSE"><img src="https://img.shields.io/badge/license-AGPL--3.0-blue" alt="AGPL-3.0 license"></a>
  14. <a href="https://github.com/Aletheore/Aletheore/actions/workflows/tests.yml"><img src="https://github.com/Aletheore/Aletheore/actions/workflows/tests.yml/badge.svg" alt="Tests"></a>
  15. <a href="https://codecov.io/gh/Aletheore/Aletheore"><img src="https://codecov.io/gh/Aletheore/Aletheore/graph/badge.svg" alt="Coverage"></a>
  16. <a href="https://securityscorecards.dev/viewer/?uri=github.com/Aletheore/Aletheore"><img src="https://api.securityscorecards.dev/projects/github.com/Aletheore/Aletheore/badge" alt="OpenSSF Scorecard"></a>
  17. <a href="https://pepy.tech/projects/aletheore"><img src="https://static.pepy.tech/personalized-badge/aletheore?period=total&amp;units=INTERNATIONAL_SYSTEM&amp;left_color=BLACK&amp;right_color=GREEN&amp;left_text=downloads" alt="PyPI downloads"></a>
  18. <a href="https://mcpvault.io/servers/aletheore/health?utm_source=external_badge&amp;utm_medium=referral&amp;utm_campaign=mcp_health_report"><img src="https://mcpvault.io/badge/aletheore.svg" alt="MCPVault status"></a>
  19. <a href="https://deepwiki.com/Aletheore/Aletheore"><img src="https://deepwiki.com/badge.svg" alt="Ask DeepWiki"></a>
  20. </p>
  21. <p align="center">
  22. <a href="https://trendshift.io/repositories/221622?utm_source=trendshift-badge&amp;utm_medium=badge&amp;utm_campaign=badge-trendshift-221622" target="_blank" rel="noopener noreferrer"><img src="https://trendshift.io/api/badge/trendshift/repositories/221622/daily?language=Python" alt="Aletheore/Aletheore | Trendshift" width="250" height="55"></a>
  23. </p>
  24. <p align="center">
  25. <a href="src/README.md"><img src="https://img.shields.io/badge/Docs-CLI_reference-3276b8?style=flat-square&amp;logo=readthedocs&amp;logoColor=white" alt="CLI documentation"></a>
  26. <a href="https://github.com/apps/aletheore/installations/new"><img src="https://img.shields.io/badge/GitHub_App-Install-dd8034?style=flat-square&amp;logo=github&amp;logoColor=white" alt="Install the GitHub App"></a>
  27. <a href="https://github.com/marketplace/actions/aletheore"><img src="https://img.shields.io/badge/Marketplace-Action-2088ff?style=flat-square&amp;logo=githubactions&amp;logoColor=white" alt="GitHub Marketplace Action"></a>
  28. <a href="https://github.com/sponsors/ArihantK15"><img src="https://img.shields.io/badge/Sponsor-Support-ea4aaa?style=flat-square&amp;logo=githubsponsors&amp;logoColor=white" alt="Sponsor development"></a>
  29. <a href="https://github.com/Aletheore/Aletheore"><img src="https://img.shields.io/github/stars/Aletheore/Aletheore?style=flat-square&amp;label=Star&amp;color=e3b341" alt="GitHub stars"></a>
  30. </p>
  31. <p align="center">
  32. <a href="#quickstart">Run locally</a> ·
  33. <a href="https://www.aletheore.com/#walkthrough">Watch the walkthrough</a> ·
  34. <a href="#see-the-evidence">Explore the evidence</a>
  35. </p>
  36. ## See the workflow
  37. ![Scan → Evidence graph → Coding agent → PR review](assets/readme-workflow.svg)
  38. [Watch the 95-second developer walkthrough →](https://www.aletheore.com/#walkthrough)
  39. <!-- GitHub requires a standalone attachment URL to render the video player. -->
  40. <!-- markdownlint-disable-next-line MD034 -->
  41. https://github.com/user-attachments/assets/91b58344-d5b7-4be5-b71f-32f1da8499ed
  42. With background music and on-screen explanations. Follow a scan of Aletheore's own CLI source, inspect dependencies and related tests,
  43. then see how the evidence connects to MCP and PR review. The walkthrough separates
  44. captured local output from explanations of hosted features.
  45. ## Quickstart
  46. Requires **Python 3.11–3.14** and [pipx](https://pipx.pypa.io/latest/how-to/install-pipx.html).
  47. Run these commands from a repository you want to inspect:
  48. ```bash
  49. pipx install aletheore
  50. aletheore scan .
  51. aletheore query hotspots
  52. aletheore dashboard .
  53. ```
  54. Open the dashboard at the local URL printed in your terminal. The scan writes
  55. `.aletheore/air.json`, a compact `.aletheore/air.toon`, and history snapshots.
  56. The deterministic scanner does not call an LLM. Local scanning and structural queries
  57. need no Aletheore account or model API key. Registry lookups and optional scanner integrations
  58. can use the network; see [Data and network behavior](#data-and-network-behavior).
  59. Already installed? Update with `pipx upgrade aletheore`.
  60. For a virtual environment or source installation, see the [setup guide](src/README.md#setup).
  61. ### Try the built-in demo
  62. ```bash
  63. aletheore demo
  64. ```
  65. The demo creates a small synthetic Python repository with local Git history and runs
  66. the real scanner to build reusable evidence, retrieve source, trace imports, and execute
  67. a local MCP tool call. In a terminal, arrow-key menus guide one screen at a time,
  68. with actions to open the sample dashboard or try your own repository. Use `aletheore demo --plain`
  69. for a printable report; piped output also runs without prompts.
  70. You can also select **Take the guided demo** from the `aletheore` home menu.
  71. Tests are suggested, not executed. Git must be installed; no account,
  72. model, or repository clone is needed. The sample and evidence remain in a temporary
  73. directory for follow-up queries and the dashboard. Delete that directory when finished.
  74. ## See the evidence
  75. ### Explore a repository's dependencies
  76. [![Local Aletheore dashboard showing the dependency graph of its CLI source](assets/readme-dependencies.png)](assets/readme-dependencies.png)
  77. A real local scan of Aletheore's CLI source. Hover modules in the dashboard to explore
  78. resolved imports. Security checks were disabled for this capture; graph nodes do not
  79. represent a clean security verdict.
  80. ### Read a finding where you review code
  81. [![Aletheore bot finding on GitHub PR 1128, describing a count-parsing behavior regression](assets/readme-pr-finding.png)](https://github.com/Aletheore/Aletheore/pull/1128)
  82. An actual bot comment on [PR #1128](https://github.com/Aletheore/Aletheore/pull/1128).
  83. The screenshot shows the review surface; a finding remains something to investigate.
  84. ### Explore AIRview
  85. [![AIRview public demo showing connected Aletheore modules and their import relationships](assets/readme-airview.png)](https://www.aletheore.com/#live-title)
  86. The public AIRview demo, captured from the website using Aletheore's own module graph.
  87. [Try the interactive version](https://www.aletheore.com/#live-title) to drag modules and
  88. trace imports. This is the public demo rather than an authenticated hosted workspace.
  89. ## Start with a question
  90. Run a scan first. Replace the example paths and symbol with names from your repository.
  91. | What you need to know | Command |
  92. | --- | --- |
  93. | Where is a function defined? | `aletheore locate find_ownership` |
  94. | Who imports this file, directly or indirectly? | `aletheore dependents src/example.py` |
  95. | Where is this symbol referenced? | `aletheore usages parse_config` |
  96. | Which tests are related to this file? | `aletheore tests-for src/example.py` |
  97. | Which files change frequently? | `aletheore query hotspots` |
  98. | Who has contributed to a file? | `aletheore query ownership src/example.py` |
  99. | Which endpoints are mapped? | `aletheore query endpoints` |
  100. | Which secret findings need review? | `aletheore query secrets` |
  101. | Are there circular imports? | `aletheore cycles` |
  102. `dependents` follows resolved import edges. `tests-for` identifies candidates from import
  103. relationships and naming conventions; it does not execute tests or establish coverage.
  104. Ownership reflects Git history, rather than an assignment of responsibility.
  105. Use `aletheore query` to list available query kinds and `aletheore COMMAND --help` for options.
  106. ## Give your coding agent repository evidence
  107. ```bash
  108. aletheore mcp-install . --target cursor
  109. ```
  110. This writes client configuration so Cursor can launch the repository's MCP server.
  111. Restart or reload the client as needed. Other supported targets include Claude Code,
  112. VS Code, Kiro, Opencode, Antigravity, Codex CLI, and Claude Desktop; list the current
  113. options with `aletheore mcp-install --help`.
  114. An agent can inspect symbols, imports, dependents, owners, endpoints, and related evidence
  115. without starting each investigation from an unstructured repository dump.
  116. For example, ask your agent:
  117. > Before changing this function, use Aletheore to locate its definition, inspect its
  118. > references and import dependents, and identify candidate tests. Cite the evidence and
  119. > distinguish resolved relationships from uncertainty.
  120. For clients you configure manually, the server command is `aletheore mcp .`.
  121. Optional AI answering, semantic indexing, and external tools have their own setup and
  122. network requirements. See the [MCP guide](src/README.md#aletheore-mcp-path).
  123. ## Check and undo what an agent changes
  124. Shield is a local safety net for AI-written changes in a Git repository. It makes no
  125. model call.
  126. ```bash
  127. pipx install aletheore # or: pip install aletheore
  128. aletheore shield
  129. ```
  130. `aletheore shield` shows every change it plans, with a diff for each file, then waits.
  131. Type `yes` to set it up. Nothing is written before that. Once Shield is on, the same command shows
  132. its status. The explicit forms are `aletheore shield setup` and `aletheore shield status`; setup
  133. run again shows only what needs updating. Setup changes:
  134. - `.claude/settings.local.json`: Claude Code hooks for four events (before an edit, after an
  135. edit, end of turn, end of session), each the Python interpreter plus arguments, so no shell
  136. quoting is involved. This file is personal and is not committed. Entries an earlier Shield
  137. wrote as one shell-command string are noted by `aletheore shield status`; `aletheore shield setup`
  138. updates them in place.
  139. - The Git `pre-commit` hook: a marked block that prints Shield's report and never fails the commit.
  140. Tools that generate Git hooks (pre-commit, lefthook, husky) can overwrite that block;
  141. `aletheore shield status` then notes that the Git hook is missing, and `aletheore shield setup`
  142. puts it back.
  143. - `.git/info/exclude`: a marked block that keeps Shield's files out of `git status`.
  144. `.gitignore` is not touched.
  145. - `.aletheore/shield/config.json`, and private records under the Git directory.
  146. - A first local scan into `.aletheore/`, if the repository has no evidence yet.
  147. What it does:
  148. - **Guard.** After edits, at the end of a turn and at commit, it reports new or suspicious
  149. dependencies (checked against PyPI and npm), files the change reaches and candidate tests,
  150. signature changes (stated per file that imports the module, not per call site), and new secrets
  151. and import cycles. Vulnerability and layer-convention findings appear only when the evidence came
  152. from a full `aletheore scan`.
  153. - **Checkpoints.** Before an agent edits, Shield saves the working tree as a Git commit under
  154. `refs/aletheore/checkpoints/`. Your branches, index and stash are not touched. Put files back
  155. with `aletheore shield undo`; it saves a safety checkpoint first and never deletes a file.
  156. - **Receipts.** At the end of a session, `.aletheore/shield/receipts/` gets a file listing
  157. what changed and what the guard found.
  158. What it does not do:
  159. - It never blocks a commit or an agent turn.
  160. - It does not run the candidate tests. Dependency and signature checks work at the import
  161. level, not the call level.
  162. - Only PyPI and npm are checked. Any other dependency is reported as "not checked".
  163. - It does not refresh stale scan evidence inline; checks that need fresh evidence say they were
  164. skipped.
  165. - Each hook has a time limit. Anything the guard could not finish in time is listed as not checked,
  166. never reported as a finding. Measured on two 9,400-file repositories: about 0.6 s per hook on a
  167. copy of this repository and 0.45-0.8 s on a generated one (1.2-1.3 s at session end on both).
  168. Registry lookups send only the package name to `pypi.org` or `registry.npmjs.org`, never versions,
  169. paths or source. They run only at turn end, at commit and in `aletheore shield check`. Turn them off
  170. with `ALETHEORE_SHIELD_OFFLINE=1` or `"registry_lookups": false` in
  171. `.aletheore/shield/config.json`. With lookups on, the answers are cached in
  172. `~/.cache/aletheore/shield-registry-cache.json` (under your user profile on Windows), outside the
  173. repository; `off --purge` leaves that file. Checkpoint refs are local; `git push --mirror` pushes every ref
  174. including them, so avoid it or delete the refs first. Undo writes files the way `git checkout`
  175. would, following your line-ending and filter settings.
  176. `aletheore shield off` removes the hooks, config and marked blocks and keeps checkpoints and
  177. receipts; `--purge` deletes those too. Scan evidence in `.aletheore/` stays, and so does a
  178. one-line git exclude for it until you delete `.aletheore/` and run `off` again.
  179. Shield targets macOS, Linux and Windows; CI runs the unit tests and a CLI smoke test of setup, the
  180. four hooks and `off` on all three. It has not been run against a real Claude Code session on Windows. See the
  181. [command reference](src/README.md#aletheore-shield) for options, limits and exit codes.
  182. ## What you can use
  183. | Surface | Purpose | Start here |
  184. | --- | --- | --- |
  185. | Local CLI | Scan, locate code, inspect risks, and compare evidence | `aletheore scan .` |
  186. | Local dashboard | Explore dependency and cluster graphs and scan history | `aletheore dashboard .` |
  187. | MCP server | Let a coding agent query repository evidence | `aletheore mcp-install --help` |
  188. | AI audit | Generate a report using a configured coding-agent CLI or API provider | `aletheore audit --help` |
  189. | Hallbook | Search the bundled coding-agent skill catalog | `aletheore hallbook search "code review"` |
  190. | Shield | Check and undo what a coding agent changes in a Git repository | `aletheore shield` |
  191. | Agent context tools | Inspect tool overhead and local context savings | `aletheore tokens meter` |
  192. | GitHub Action | Report new and resolved findings between a PR's base and head | [Action setup](#run-in-github-actions) |
  193. | Hosted GitHub App | Run PR reviews and use managed repository features | [Install the app](https://github.com/apps/aletheore/installations/new) |
  194. Hallbook skills have individual instructions, dependencies, and licenses; review a skill
  195. before installing or executing it. Token auditing can invoke your configured agent;
  196. context profiles are optional and change which tools that agent can access.
  197. ## Review changes in GitHub
  198. The hosted GitHub App adds PR reviews, managed audits, AIRview architecture pages,
  199. AI-marked symbol documentation, and endpoint monitoring with source context.
  200. Availability depends on the selected plan. Free AI reviews are globally rate-limited and
  201. subject to availability. See [current plans and limits](https://www.aletheore.com/pricing)
  202. rather than relying on a price copied into this README.
  203. [Install the Aletheore GitHub App](https://github.com/apps/aletheore/installations/new)
  204. and choose the repositories to connect.
  205. ### Run in GitHub Actions
  206. <details>
  207. <summary><strong>GitHub Actions workflow and execution notes</strong></summary>
  208. For a deterministic PR diff in your own workflow:
  209. ```yaml
  210. name: Aletheore
  211. on: [pull_request]
  212. permissions:
  213. contents: read
  214. pull-requests: write
  215. jobs:
  216. evidence:
  217. runs-on: ubuntu-latest
  218. steps:
  219. - uses: Aletheore/Aletheore@v0.13.0
  220. with:
  221. fail-on-new-secrets: true
  222. ```
  223. The Action scans both refs and reports new/resolved secrets, dependency vulnerabilities,
  224. and layer-convention violations. It runs `scan` and `diff`, rather than an AI audit.
  225. The example pins an existing release; review and pin a commit SHA for your own deployment
  226. policy. Fork PRs can have read-only tokens: comment posting may be unavailable even when
  227. analysis succeeds. See [Action inputs](action.yml) and the [CLI reference](src/README.md).
  228. </details>
  229. ## What the scanner understands
  230. <p>Dependency graph support, with language-specific resolution limits:</p>
  231. <p>
  232. <a href="src/README.md"><img src="https://img.shields.io/badge/Python-3776AB?style=flat-square&amp;logo=python&amp;logoColor=white" alt="Python dependency graph support"></a>
  233. <a href="src/README.md"><img src="https://img.shields.io/badge/JavaScript-c4a800?style=flat-square&amp;logo=javascript&amp;logoColor=white" alt="JavaScript dependency graph support"></a>
  234. <a href="src/README.md"><img src="https://img.shields.io/badge/TypeScript-3178C6?style=flat-square&amp;logo=typescript&amp;logoColor=white" alt="TypeScript dependency graph support"></a>
  235. <a href="src/README.md"><img src="https://img.shields.io/badge/Go-007D9C?style=flat-square&amp;logo=go&amp;logoColor=white" alt="Go dependency graph support"></a>
  236. <a href="src/README.md"><img src="https://img.shields.io/badge/Rust-9b4f23?style=flat-square&amp;logo=rust&amp;logoColor=white" alt="Rust dependency graph support"></a>
  237. <a href="src/README.md"><img src="https://img.shields.io/badge/Java-b85e00?style=flat-square&amp;logo=openjdk&amp;logoColor=white" alt="Java dependency graph support"></a>
  238. <a href="src/README.md"><img src="https://img.shields.io/badge/Kotlin-7F52FF?style=flat-square&amp;logo=kotlin&amp;logoColor=white" alt="Kotlin dependency graph support"></a>
  239. <a href="src/README.md"><img src="https://img.shields.io/badge/Ruby-CC342D?style=flat-square&amp;logo=ruby&amp;logoColor=white" alt="Ruby dependency graph support"></a>
  240. <a href="src/README.md"><img src="https://img.shields.io/badge/PHP-777BB4?style=flat-square&amp;logo=php&amp;logoColor=white" alt="PHP dependency graph support"></a>
  241. <a href="src/README.md"><img src="https://img.shields.io/badge/C-5969ab?style=flat-square&amp;logo=c&amp;logoColor=white" alt="C dependency graph support"></a>
  242. <a href="src/README.md"><img src="https://img.shields.io/badge/C%2B%2B-00599C?style=flat-square&amp;logo=cplusplus&amp;logoColor=white" alt="C++ dependency graph support"></a>
  243. <a href="src/README.md"><img src="https://img.shields.io/badge/C%23-512BD4?style=flat-square&amp;logo=dotnet&amp;logoColor=white" alt="C# dependency graph support"></a>
  244. <a href="src/README.md"><img src="https://img.shields.io/badge/Swift-c74b27?style=flat-square&amp;logo=swift&amp;logoColor=white" alt="Swift dependency graph support"></a>
  245. </p>
  246. <details>
  247. <summary><strong>Language support, available evidence, and analysis limits</strong></summary>
  248. Dependency graphs support **Python, JavaScript/JSX, TypeScript/TSX, Go, Rust, Java, Kotlin,
  249. Ruby, PHP, C, C++, C#, and Swift**, with language-specific resolution limits.
  250. Secrets and Git analysis can still apply to other source files.
  251. Dependency checks depend on supported manifests, resolved versions, and registry coverage.
  252. The evidence can include imports, symbols, clusters, Git ownership and activity,
  253. secret findings, dependency vulnerabilities and licenses, static analysis, endpoints,
  254. database schema, infrastructure, and error handling. Some checks depend on installed
  255. external scanners or explicit configuration. Missing tools and unsupported analysis
  256. must be distinguished from a clean result.
  257. Static evidence is a starting point for investigation. Dynamic dispatch, runtime configuration,
  258. external services, and unresolved imports can leave gaps. A source citation makes a claim
  259. inspectable; it does not by itself prove that a bug exists or that a change is safe.
  260. Read [resolution details and configuration](src/README.md) for the limits that apply to your language.
  261. </details>
  262. ## Data and network behavior
  263. Local scans build evidence on your machine. Enabled registry checks, optional integrations,
  264. crash reporting, and AI features have their own network behavior.
  265. <details>
  266. <summary><strong>Network requests, crash reporting, and offline scan flags</strong></summary>
  267. The local deterministic scan builds evidence on your machine. Its network behavior depends
  268. on enabled checks and integrations:
  269. - Dependency vulnerability and license checks contact OSV and package registries.
  270. - Semgrep can fetch rules and send its own metrics; optional integrations such as SonarQube
  271. have separate submission behavior.
  272. - CLI startup can check PyPI for updates. Set `ALETHEORE_NO_UPDATE_CHECK=1` to disable that check.
  273. - Crash reporting is enabled by default and can be disabled with
  274. `aletheore config crash-reporting off` or `ALETHEORE_CRASH_REPORTING=0`.
  275. - AI audits, hosted features, and configured semantic services send the context required
  276. by the selected workflow to their configured services. Local evidence can contain
  277. sensitive metadata or source excerpts; review it before sharing.
  278. Before scanning, inspect potential traffic for the resolved configuration:
  279. ```bash
  280. aletheore scan . --explain-network
  281. ```
  282. This prints the conditional network paths and exits without scanning. It is an
  283. explanation of configured behavior, rather than a firewall or packet trace.
  284. To skip registry and static-scanner checks for a local scan:
  285. ```bash
  286. aletheore scan . --no-check-vulnerabilities --no-check-licenses --no-check-static-analysis
  287. ```
  288. These scan flags do not configure every other command or service. Review
  289. [CLI configuration and crash reporting](src/README.md#crash-reporting),
  290. [security information](SECURITY.md), and the hosted [privacy policy](https://www.aletheore.com/privacy)
  291. for the workflow you choose.
  292. </details>
  293. ## Evidence and benchmarks
  294. Explore [published scan examples](https://www.aletheore.com/dogfooding) and
  295. [benchmarks with methodology and limits](https://www.aletheore.com/benchmarks).
  296. The separate [benchmark repository](https://github.com/Aletheore/aletheore-benchmarks)
  297. contains the PR-review evaluation harness. Results depend on repository, task, model,
  298. and sample; they do not guarantee the same result on your code.
  299. ## Contribute or get help
  300. - [Report a bug or request a feature](https://github.com/Aletheore/Aletheore/issues).
  301. - Read [CONTRIBUTING.md](CONTRIBUTING.md) to work on the project.
  302. - Use [SECURITY.md](SECURITY.md) for vulnerability reports.
  303. - [Sponsor development](https://github.com/sponsors/ArihantK15).
  304. <details>
  305. <summary><strong>Repository map</strong></summary>
  306. | Directory | Contents |
  307. | --- | --- |
  308. | [`src/`](src/) | CLI implementation and command reference |
  309. | [`site/`](site/) | Next.js marketing site |
  310. | [`docs/operations/`](docs/operations/) | Operational baselines and runbooks |
  311. | [`benchmarks/`](benchmarks/) | Repository benchmark material |
  312. The hosted application is maintained separately from this public repository.
  313. </details>
  314. ## Licensing
  315. The CLI and other code in this repository are open source under the [GNU Affero General Public License v3.0](LICENSE)
  316. (AGPL-3.0). You can use, study, modify, and redistribute it, including at a company and
  317. for internal tooling, as long as you follow the AGPL. The part that matters most:
  318. - If you modify Aletheore and convey that covered work, or provide it for network interaction in
  319. circumstances covered by AGPL section 13, follow the AGPL's corresponding-source and notice
  320. requirements for the covered work.
  321. - Independent code and separate components may remain under their own licenses; whether a
  322. combination is a covered work depends on the AGPL and the facts of the distribution.
  323. - Running the unmodified CLI or Action on your own code does not put your code under the AGPL.
  324. If those terms don't fit, for example you want to embed Aletheore in a closed-source product
  325. or run a modified version as a service without publishing it, a commercial license is
  326. available. See [COMMERCIAL-LICENSE.md](COMMERCIAL-LICENSE.md), or email
  327. [arihantkaul@outlook.com](mailto:arihantkaul@outlook.com). The hosted, paid tier is
  328. [Aletheore AIR](https://aletheore.com).
  329. Copyright (C) 2026 Arihant Kaul. See [NOTICE](NOTICE).
  330. Releases through 0.8.12 were Apache 2.0, and 0.8.13 through the version before this change were PolyForm
  331. Noncommercial 1.0.0. Copies you already received keep the license they came with.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.