Skip to content
Back to search

legacy2modern

Forall (∀) is a coding harness from Astrio that helps developers build correct software by generating spec-driven code alongside machine-checkable proofs.

Safety scan

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

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/astrio-ai--legacy2modern/badge.svg)](/listings/astrio-ai--legacy2modern)

HTML

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

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

Full coding agent — specs, proofs, and workflow in your terminal.

curl -fsSL https://forall.astrio.app/install.sh | bash
forall

Add `~/.local/bin` to your `PATH` if needed, then run `forall --version`.

On first launch, sign in with your [Forall account](https://forall.astrio.app) — your browser opens, no API key to paste. Chat on your plan's hosted models, or bring your own model API key (OpenAI, OpenRouter, Anthropic (Claude), Google Gemini, Azure OpenAI, or Claude via Amazon Bedrock). Then `forall init` in a git repo and start working.

> **Note:** A binary release must exist on [GitHub Releases](https://github.com/astrio-labs/forall-mcp/releases) before install succeeds.

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 · 125 lines · 1 finding marked

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

  1. <p align="center">
  2. <a href="https://github.com/astrio-labs/forall-mcp">
  3. <picture>
  4. <source srcset="assets/forall_bg.png">
  5. <img src="assets/forall_bg.png" alt="Forall Background">
  6. </picture>
  7. </a>
  8. </p>
  9. <p align="center">
  10. <a href="./LICENSE"><img alt="License: Apache-2.0" src="https://img.shields.io/badge/License-Apache%202.0-blue.svg?style=flat-square" /></a>
  11. <a href="https://discord.com/invite/gESuZkdD5R"><img alt="Discord" src="https://img.shields.io/badge/Discord-community-5865F2?style=flat-square&logo=discord&logoColor=white" /></a>
  12. <a href="https://x.com/astriolabs"><img src="https://img.shields.io/badge/Follow%20on%20X-222021?logo=x&logoColor=white" alt="Follow on X"></a>
  13. </p>
  14. <div align="center">
  15. <img alt="Forall CLI" src="assets/forall-cli.png" width="800" />
  16. </div>
  17. ## Why Forall exists
  18. Review has always been the bottleneck in software. It is now the failure point,
  19. because code is produced faster than anyone can check it. Tests sample a
  20. handful of inputs. Types constrain shape. Neither tells you whether the code
  21. does what it was supposed to do.
  22. Formal verification answers that question, as far as your specification states
  23. it, and it never failed on capability. Provers have been checking real programs
  24. for years. What kept them out of ordinary engineering was adoption cost.
  25. Writing the specifications, contracts and invariants a prover needs was more
  26. tedious than writing the code itself. That is precisely the work language
  27. models are now good at. The barrier was labour, and labour just got cheap.
  28. Evidence can therefore become a build artifact rather than something
  29. reconstructed by hand long after the code is done. Regulated work already
  30. depends on it. Standards such as IEC 62304 and DO-178C require traceability
  31. from each requirement to the verification that discharges it. Mission-critical
  32. code should carry that evidence the way a paper carries its references,
  33. attached to the specific claim it supports.
  34. A green mark that lies is worse than no mark. A proof is only as strong as the
  35. contract it discharges, and property testing only samples. Those differences
  36. matter, so Forall reports four levels of evidence instead of a pass and a fail,
  37. grading every requirement by the strongest evidence a machine actually
  38. produced, never by what was claimed.
  39. ## Two ways to use Forall
  40. ### 1. Install Forall CLI
  41. Full coding agent — specs, proofs, and workflow in your terminal.
  42. ```bash
  43. curl -fsSL https://forall.astrio.app/install.sh | bash
    • Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
    • Line 54 on GitHub
  44. forall
  45. ```
  46. Add `~/.local/bin` to your `PATH` if needed, then run `forall --version`.
  47. On first launch, sign in with your [Forall account](https://forall.astrio.app) — your browser opens, no API key to paste. Chat on your plan's hosted models, or bring your own model API key (OpenAI, OpenRouter, Anthropic (Claude), Google Gemini, Azure OpenAI, or Claude via Amazon Bedrock). Then `forall init` in a git repo and start working.
  48. > **Note:** A binary release must exist on [GitHub Releases](https://github.com/astrio-labs/forall-mcp/releases) before install succeeds.
  49. ### 2. MCP verify-only
  50. Stay on Cursor, Claude Code, or any MCP client — add hosted verification via MCP. **Do not** install the CLI.
  51. 1. Create an API key at [forall.astrio.app/dashboard](https://forall.astrio.app/dashboard)
  52. 2. Add to your MCP client:
  53. ```json
  54. {
  55. "mcpServers": {
  56. "forall": {
  57. "command": "npx",
  58. "args": ["-y", "@astrio/forall-mcp"],
  59. "env": {
  60. "FORALL_API_KEY": "forall_..."
  61. }
  62. }
  63. }
  64. }
  65. ```
  66. Your coding agent edits the workspace from verify reports. See [docs/getting-started.md](docs/getting-started.md) and [docs/hosted-mcp.md](docs/hosted-mcp.md).
  67. ## Supported programming languages
  68. Forall grades every requirement by the strongest evidence a machine actually
  69. produced for it. Not every rung is reachable in every language, because the
  70. rung depends on the tool behind it:
  71. | | Spec tracked | Property tested | Contracted | Proved |
  72. | --- | :---: | :---: | :---: | :---: |
  73. | **TypeScript** | ✓ | ✓ | ✓ | ✓ |
  74. | **Python** | ✓ | ✓ | ✓ | ✗ |
  75. | **Rust** | ✓ | ✗ | ✓ | ✓ |
  76. | **Java** | ✓ | ✗ | ✓ | ✓ |
  77. | **C** | ✓ | ✗ | ✓ | ✓ |
  78. - **Spec tracked** — a requirement cites this code.
  79. - **Property tested** — a generator ran over many inputs and found no
  80. counterexample. Statistical evidence, honestly ranked below a proof.
  81. - **Contracted** — a machine-checkable contract is written against the code,
  82. but nothing has confirmed it yet.
  83. - **Proved** — a prover discharged that contract's obligations.
  84. We are expanding to more languages, and to filling in more of this table for the languages already listed, based on demand.
  85. ## Telemetry
  86. First-party builds send product usage analytics — feature and reliability events, never your code or prompts. Opt out any time in `~/.forall/config.toml`:
  87. ```toml
  88. [analytics]
  89. enabled = false
  90. ```
  91. ## Connect
  92. Join our [Discord](https://discord.com/invite/gESuZkdD5R) and [X](https://x.com/astriolabs) communities.
  93. ## License
  94. This repository is licensed under the [Apache-2.0 License](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

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