Skip to content
Back to search

noir

Hunt every Endpoint in your code, expose Shadow APIs, map the Attack Surface.

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/owasp-noir/noir 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/owasp-noir/noir'

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/owasp-noir--noir/badge.svg)](/listings/owasp-noir--noir)

HTML

<a href="/listings/owasp-noir--noir"><img src="/api/listings/owasp-noir--noir/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 · 102 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. <div align="center">
  2. <picture>
  3. <source media="(prefers-color-scheme: dark)" srcset="https://github.com/owasp-noir/noir/assets/13212227/04aee7d0-c224-481b-8d79-2dbdcf3ad84b" width="500px;">
  4. <source media="(prefers-color-scheme: light)" srcset="https://github.com/owasp-noir/noir/assets/13212227/0577860e-3d7e-4294-8f1f-dc7b87ce2b2b" width="500px;">
  5. <img alt="OWASP Noir Logo" src="https://github.com/owasp-noir/noir/assets/13212227/04aee7d0-c224-481b-8d79-2dbdcf3ad84b" width="500px;">
  6. </picture>
  7. <p>Hunt every Endpoint in your code, expose Shadow APIs, map the Attack Surface.</p>
  8. </div>
  9. <p align="center">
  10. <a href="https://github.com/owasp-noir/noir/releases">
  11. <img src="https://img.shields.io/github/v/release/owasp-noir/noir?style=for-the-badge&color=black&labelColor=black&logo=web"></a>
  12. <a href="https://crystal-lang.org">
  13. <img src="https://img.shields.io/badge/Crystal-000000?style=for-the-badge&logo=crystal&logoColor=white"></a>
  14. <a href="https://owasp.org/projects/noir">
  15. <img src="https://img.shields.io/badge/OWASP-000000?style=for-the-badge&logo=owasp&logoColor=white"></a>
  16. <a href="https://www.bestpractices.dev/projects/14203">
  17. <img src="https://img.shields.io/badge/OpenSSF-Best%20Practices-000000?style=for-the-badge&labelColor=black"></a>
  18. <a href="https://github.com/owasp-noir/noir/blob/main/.github/CONTRIBUTING.md">
  19. <img src="https://img.shields.io/badge/CONTRIBUTIONS-WELCOME-000000?style=for-the-badge&labelColor=black"></a>
  20. </p>
  21. <p align="center">
  22. <a href="https://owasp-noir.github.io/noir/">Documentation</a> •
  23. <a href="https://owasp-noir.github.io/noir/get_started/installation/">Installation</a> •
  24. <a href="#usage">Usage</a> •
  25. <a href="https://owasp-noir.github.io/noir/usage/github_action/">GitHub Action</a> •
  26. <a href="#contributing">Contributing</a> •
  27. <a href="./CHANGELOG.md">Changelog</a>
  28. </p>
  29. Noir is a SAST tool that reads source code and lists the endpoints an application exposes: paths, methods, parameters, headers, cookies, and the source files behind them. Shadow APIs, deprecated routes, and undocumented handlers are in the same inventory.
  30. The inventory has three readers:
  31. - **Human reviewers** start from attacker-reachable entry points instead of the whole repo.
  32. - **AI auditors** get the same list plus per-endpoint review context (`--include callee`, `--ai-context`).
  33. - **DAST tools** (ZAP, Burp Suite, Caido, Gori) get routes a crawler would never reach.
  34. ## What Noir does
  35. - **Endpoint extraction.** Static analysis across [264 frameworks](https://owasp-noir.github.io/noir/usage/supported/language_and_frameworks/).
  36. - **LLM fallback.** OpenAI, Ollama, and other providers cover frameworks the static rules don't.
  37. - **Output formats.** JSON, YAML, OpenAPI, SARIF, cURL, Postman, HTML, and more.
  38. - **DAST integration.** Send endpoints to ZAP, Burp Suite, Caido, or Gori through a proxy, or export OpenAPI.
  39. - **AI review context.** `--include callee` adds the functions each handler calls; `--ai-context` adds guards, sources, sinks, validators, and signals.
  40. - **CI/CD.** GitHub Action, SARIF output, and exit codes.
  41. ## Usage
  42. ```bash
  43. brew install noir
  44. noir scan <source_dir>
  45. ```
  46. ![](/docs/content/get_started/overview/noir-usage.jpg)
  47. Other install methods (Snap, Docker, npm, Nix, packages) are on the [Installation](https://owasp-noir.github.io/noir/get_started/installation/) page. Run `noir -h` for every flag, or see the [documentation](https://owasp-noir.github.io/noir/) and the [GitHub Action](https://owasp-noir.github.io/noir/usage/github_action/) page.
  48. ## Roadmap
  49. Noir started as a way to hand DAST tools the routes found in source code. The same inventory now serves human reviewers and AI auditors too, and the roadmap treats all three equally:
  50. - Broaden language and framework coverage, with per-framework fixtures to check accuracy.
  51. - Use LLMs where static analysis can't reach.
  52. - Enrich the per-endpoint review context (guards, callees, sinks, validators, signals).
  53. - Keep DAST integration first-class: OpenAPI, proxy targets, and hand-offs to ZAP, Burp Suite, Caido, and Gori.
  54. ## OWASP Project
  55. OWASP Noir joined the OWASP Foundation in **June 2024**.
  56. - Official project page: [https://owasp.org/projects/noir](https://owasp.org/projects/noir)
  57. - OWASP Nest: [https://nest.owasp.org/projects/noir](https://nest.owasp.org/projects/noir)
  58. ## News & Updates
  59. * May 2026: Released **v1.0.0**, the stable 1.x line with a verb-based CLI.
  60. * May 2026: Refreshed the roadmap to serve human reviewers, AI auditors, and DAST tools equally.
  61. * August 2025: Presented at the OWASP Seoul Meetup. ([Open Source Gardening](https://owasp-noir.github.io/noir/community/media/#featured-owasp-seoul-aug-2025-open-source-gardening))
  62. * November 2024: Published a guest blog post ["Powering Up DAST with ZAP and Noir"](https://www.zaproxy.org/blog/2024-11-11-powering-up-dast-with-zap-and-noir/) on the ZAP blog.
  63. * June 2024: Joined OWASP as OWASP Noir
  64. * Renamed the GitHub organization from noir-cr to owasp-noir
  65. * Transitioned to co-leadership with [@ksg97031](https://github.com/ksg97031)
  66. * November 2023: Moved the Noir repository to the noir-cr GitHub organization.
  67. * August 2023: Started as [@hahwul](https://github.com/hahwul)'s personal project.
  68. ## Core Team
  69. [![](./docs/static/CORETEAM.svg)](https://owasp-noir.github.io/noir/resources/contact/)
  70. ## Contributing
  71. Noir is an open-source project made with ❤️.
  72. To contribute, see [CONTRIBUTING.md](./.github/CONTRIBUTING.md) and open a pull request.
  73. [![](./docs/static/CONTRIBUTORS.svg)](https://github.com/owasp-noir/noir/graphs/contributors)
  74. ## Mascot
  75. | ![](docs/static/images/mascot/hak-wave.webp "Hak") | Hak (학) is the Noir mascot: a crane, which is what "학" means in Korean. <br><br> More artwork is in the [noir-artwork repository](https://github.com/owasp-noir/noir-artwork).|
  76. | -------------- | -------------- |

Ratings and comments

Sign in to rate this skill.

Sign in

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