[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f26tvzst6j75q7":3},{"code":4,"message":5,"data":6,"timestamp":48},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":22,"summary_md":23,"topic":24,"github_topics":27,"license":38,"homepage":39,"updated_at":40,"history":41},"projectdiscovery\u002Fnuclei",7,"Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.","Go",32299,3941,28,2395,[16],{"id":17,"title":18,"points":19,"comments":20,"posted_at":21},25845045,"Nuclei – http vulnerability scanning based on templates",1,0,"2021-01-20","A template-driven scanner for finding known vulnerabilities and misconfigurations across web apps, DNS, networks and cloud.","Nuclei fits teams that want repeatable, version-controlled vulnerability checks rather than ad-hoc one-off scripts. Adopt it when you can treat its templates as code you review and maintain.\n\n## The problem\n\nYou have a list of hosts, APIs or subnets and want to know whether any of them match a known weakness: an exposed panel, a CVE-shaped response, a misconfigured DNS record. Before a scanner with a shared rule format, each check tends to become its own script, with its own parsing and output, and re-running the set across a larger target list means rebuilding that glue. Nuclei changes the middle step: a YAML template declares the request and the match condition, and the CLI runs a chosen set of templates over one target, a file of targets or a whole CIDR. The result is one output stream covering many checks, with the template itself as the reusable unit.\n\n## What's different\n\nTemplates are the core abstraction. A YAML file describes a request and a matcher, and the engine handles execution across targets, so adding a check does not require writing and maintaining a separate program. The README presents the template collection as community-driven, which is the practical draw: when a vulnerability is trending, someone else may already have encoded the detection. The same engine runs over web targets, DNS, network ranges and cloud configuration, and the README shows the same command shape for a single URL, a list file and a `\u002F24` subnet. Custom templates can be passed with `-t`, which matters when you need an internal check the public set does not cover.\n\nThe trade-off is that the tool is only as useful as the templates you trust and the matchers you write. The [full documentation](https:\u002F\u002Fdocs.projectdiscovery.io\u002Ftools\u002Fnuclei\u002Frunning) describes the engine, not an accuracy guarantee, so a template that matches too broadly will produce findings you must triage by hand. The README also points to paid Pro and Enterprise editions with scale, integrations and compliance reporting; those are separate from the open-source CLI and are commercial offerings.\n\n## Who should try it\n\nA security engineer who already maintains a target inventory and wants a scan step that can be versioned alongside it is a good fit: write or select templates, run them against the list, and keep the templates in the repository. A developer who wants a one-click answer about whether a site is \"safe\" is a poor fit, because results depend on which templates ran and how their matchers were written, and interpreting them is part of the job. Teams with existing scanning platforms should check the README's Pro and Enterprise list before assuming the OSS CLI covers team workflows such as SSO and reporting.\n\n## Requirements and limitations\n\nThe README states that installing from source requires Go >= 1.27.3, so building the CLI from source assumes a recent Go toolchain; the [installation guide](https:\u002F\u002Fdocs.projectdiscovery.io\u002Ftools\u002Fnuclei\u002Finstall) is the place to check other install paths before committing. Beyond installation, the ongoing cost is template upkeep: the public collection changes as vulnerabilities are added and retired, and internal templates need review when the applications they target change. The CLI is designed for batch target lists and CIDR ranges, so operationally you need a target inventory and a place to store results. The README does not document scan-authorization or rate-limit defaults in the excerpts shown, so decide those policies yourself before pointing it at production ranges.\n\n## HotRepo's take\n\nHotRepo's tracked sample covers only 2026-10-24 (+34 stars) and 2026-10-25 (+28 stars), two daily-board observations; that is not enough to judge whether interest is rising, fading or sustained. The repository dates to 2020, so this is an established project, not a new one. Before adopting it, verify in the installation guide which install path fits your environment, since the README's source install hinges on Go >= 1.27.3.",{"slug":25,"name":26},"security","Security & Privacy",[28,29,30,31,32,25,33,34,35,36,37],"attack-surface","cve-scanner","dast","hacktoberfest","nuclei-engine","security-scanner","subdomain-takeover","vulnerability-assessment","vulnerability-detection","vulnerability-scanner","MIT","https:\u002F\u002Fdocs.projectdiscovery.io\u002Ftools\u002Fnuclei","2026-10-25T03:03:30Z",[42,46],{"date":43,"stars":44,"stars_gained":45},"2026-10-24",32291,34,{"date":47,"stars":11,"stars_gained":13},"2026-10-25",1792917889]