Install noir with Homebrew

Project links

• Homepage
• Repository
• Package manager page

Commands and aliases

• noir

Project history

The Noir README gives a clear project timeline: it started as Hahwul's personal project in August 2023, moved to the `noir-cr` GitHub organization in November 2023, joined OWASP in June 2024, and released v1.0.0 in May 2026. The same README says OWASP membership included renaming the GitHub organization from `noir-cr` to `owasp-noir` and moving to co-leadership with `ksg97031`.

The project scope widened from a WhiteBox testing aid into an inventory consumed by human reviewers, AI auditors, and DAST tools. The README describes support for 50+ frameworks, LLM fallback for unsupported routing patterns, output formats including JSON, YAML, OpenAPI, SARIF, cURL, Postman, and HTML, and direct handoffs to ZAP, Burp Suite, and Caido.

Adoption history

By 2026-07-01, GitHub metadata reported 1345 stars and 140 forks for `owasp-noir/noir`. Homebrew's formula API reported stable version 1.1.0 and 755 installs over 365 days. Those are early-project numbers, but the OWASP project page and the 1.0.0 release milestone show the tool crossing from personal/security-community project into a packaged security tool.

Noir's adoption is tied to a practical gap in API security testing: crawlers and DAST tools miss routes hidden in server code, deprecated handlers, or framework-specific routing conventions. Noir extracts the code-side route inventory so scanners and reviewers start from a better endpoint map.

How it is used

The minimal usage is `noir -b <source_dir>`. Security teams use the output to review attacker-reachable handlers, generate OpenAPI or SARIF artifacts, feed ZAP/Burp/Caido, and provide compact context to LLM-based SAST agents. CI usage is supported through a GitHub Action, SARIF output, and exit codes.

The package-nerd detail is that Noir is source-inventory glue. It is not a replacement for DAST or a general-purpose code scanner; it turns static framework knowledge into endpoint artifacts that downstream tools already understand.

Why package nerds care

Noir is still young enough that its history should stay close to maintainer-provided timelines. The useful enrichment is the OWASP transition, stable 1.x release, supported-output ecosystem, and the exact niche: static endpoint extraction for attack-surface mapping.

Timeline

• 2023-08: Noir started as Hahwul's personal project, according to the project README.
• 2023-11: The repository moved to the `noir-cr` GitHub organization.
• 2024-06: Noir joined OWASP and the organization was renamed to `owasp-noir`.
• 2026-05-24: GitHub releases list v1.0.0.
• 2026-06-15: GitHub releases list v1.1.0.
• 2026-07-01: Homebrew formula API reported stable version 1.1.0.

Related projects

• OWASP ZAP
• Burp Suite
• Caido
• SARIF
• OpenAPI

Sources

• https://api.github.com/repos/owasp-noir/noir
• https://formulae.brew.sh/api/formula/noir.json
• https://github.com/owasp-noir/noir
• https://github.com/owasp-noir/noir/releases
• https://owasp-noir.github.io/noir/
• https://owasp.org/www-project-noir/
• https://raw.githubusercontent.com/owasp-noir/noir/main/README.md