{"schema_version":1,"metadata":{"branch":"current","release":"7.9","architecture":"amd64","generated_at":"2026-09-09T04:04:41.004595+00:00","source_url":"https://cdn.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/sqlports-7.55.tgz","source_sha256":"fcdbba1b9df747882aa9bab4af20ebec8dac10655069c90f1cd4145c06e1235e","package_count":12031,"source_kind":"sqlports"},"package":{"name":"nginx-naxsi-1.30.4p2","path":"www/nginx,-naxsi","url":"/packages/current/www/nginx,-naxsi/","comment":"nginx web application firewall module","homepage":"https://nginx.org/","maintainer":"Robert Nagy <robert@openbsd.org>","description":"NAXSI means Nginx Anti XSS & SQL Injection.\n\nThe nginx nasxi module, by default, reads a small subset of simple (and\nreadable) rules containing 99% of known patterns involved in website\nvulnerabilities. For example, <, | or drop are not supposed to be part of a URI.\n\nBeing very simple, those patterns may match legitimate queries, it is the\nNaxsi's administrator duty to add specific rules that will whitelist legitimate\nbehaviours. The administrator can either add whitelists manually by analyzing\nnginx's error log, or (recommended) start the project with an intensive\nauto-learning phase that will automatically generate whitelisting rules\nregarding a website's behaviour.\n\nIn short, Naxsi behaves like a DROP-by-default firewall, the only task is to add\nrequired ACCEPT rules for the target website to work properly.\n","package_architecture":"amd64","stem":"nginx-naxsi","readme":null,"dependencies":[{"path":"www/nginx","type":"runtime","package_spec":"STEM-=1.30.4","url":"/packages/current/www/nginx/"},{"path":"lang/lua/5.1","type":"build","package_spec":"","url":"/packages/current/lang/lua/5.1/"}],"reverse_dependencies":{"count":0,"url":null},"categories":["www","lang/lua"],"flavors":["no_lua","no_modsecurity","no_njs"],"only_for_architectures":[],"not_for_architectures":[]}}