nowfound

Alternatives

Products that do what DjangoSecurityHunter does

CLI tool, detects misconfig, XSS, SQL injection risks & More

  1. 1SE

    I have been working on SQL Explorer, an open source, Django-based reporting and query tool for (gulp!) almost ten years. It's a tool that fits just right for me and many others, and I love and use almost every day. Write SQL, share results, do some analysis, get insight. No surprises. A live demo instance is here (no login or anything required): https://demo.sqlexplorer.io/ And here's a fairly unprofessional, but very enthusiastic, video tour: https://sql-explorer.s3.amazonaws.com/Sql+Explorer+5.mp4 The UI is constrained enough that there's very little to learn,…

    2024 · github.com

  2. 2DS

    2021 · django-sql-dashboard.datasette.io

  3. 3
    Opengrep340

    The open source code security engine

    2025

  4. 4DC
  5. 5MS

    I noticed the growing security concerns around MCP (https://news.ycombinator.com/item?id=43600192) and built an open source tool that can detect several patterns of tool poisoning attacks, exfiltration channels and cross-origin manipulations. MCP-Shield scans your installed servers (Cursor, Claude Desktop, etc.) and shows what each tool is trying to do at the instruction level, beyond just the API surface. It catches hidden instructions that try to read sensitive files, shadow other tools' behavior, or exfiltrate data. Example of what it detects: - Hidden instructions…

    2025 · github.com

  6. 6DC

    Over the past year I’ve been building a set of operational panels for Django: - Redis inspection - cache visibility - Celery task introspection - URL discovery and testing All of these tools have been built inside the Django admin. Instead of jumping between tools like Flower, redis-cli, Swagger, or external services, I wanted something that sits where I’m already working. I’ve grouped these under a single umbrella: Django Control Room. The idea is pretty simple: the Django admin already gives you authentication, permissions, and a familiar interface. It can also act as an operational layer…

    Feb 2026 · github.com

  7. 7

    Catch PII leaks in code & keep your PII inventory current

    2024

  8. 8WS

    http://webscanner.tk/quickscan/ Hi! I made this project over the couse of a week to help teach myself more about Django and web app development. I am studying computer security in school and web security is one of my passions. It is a tool that helps web developers ensure that they have implemented helpful security mechanisms like HTTPOnly flags, X-Frame-Options, etc. There are hundreds of tools that offer to scan websites for things like cross-site scripting, mySQL injection, etc. This tool simply looks for information that is available via one or two GET requests (the headers, protocols,…

    2013

  9. 9BB

    This is a simple single-file python program that can find basic XSS (cross-site scripting) vulnerabilities in a target url. Most XSS discovery tools use a payload refelection strategy in which payloads are injected in url parameters and the GET response is inspected for places where the payload content is reflected. This is a very low precision XSS detection strategy because most reflection does not support execution. This program uses a different approach, and instead opens the target url in a browser, tests alert(...) payloads directly in the browser context, and listens for an alert being…

    2024 · github.com

  10. 10SA

    2014 · mtford.co.uk

  11. 11

    hey guys, wanted to show one of my side projects i just made public. the idea is basically another osint tool for pentesters and bug bounty hunters. it watches certificate transparency logs and checks newly-seen domains for exposed stuff like .env files, open .git dirs, config files, db dumps and so on, and puts whatever it finds into a searchable db. you just search a domain (or part of one) and see what's exposed. it's read-only and free. one thing i've been thinking about adding is a way to register for certain keywords and get notified when something new shows up for that search. would…

    Jul 2026 · search.cerast-intelligence.com

  12. 12

    Open-source security gateway & static scanner for AI agents. Enforce role-based access control (RBAC), human-in-the-loop approvals, segregation of duties, and cryptographically signed, offline-verifiable audit logs. - makerchecker/MakerChecker

    Jul 2026 · github.com

  13. 13LE

    I started using Claude Code (claude --dangerously-skip-permissions) and Codex (codex --yolo) and realized I had no reliable way to know what they actually did. The agent's own output tells you a story, but it's the agent's story. logira records exec, file, and network events at the OS level via eBPF, scoped per run. Events are saved locally in JSONL and SQLite. It ships with default detection rules for credential access, persistence changes, suspicious exec patterns, and more. Observe-only – it never blocks. https://github.com/melonattacker/logira

    Mar 2026 · github.com

  14. 14RA

    We were using django-easy-audit to track CRUD and API events in Django. The problem: every action meant an extra database write, which slowed transactions, increased infra costs, and left us with audit tables that weren’t great for analytics. I built django-activity-audit (PyPI) to fix this: - Extends Django’s logging system with custom AUDIT and API levels. - Captures CRUD + API request/response events as structured JSON logs. - Vector tails the logs and ships them into ClickHouse. - Grafana makes them queryable and visual. This removes the extra DB writes, gives structured data ready…

    Oct 2025 · github.com

  15. 15MS

    Hi HN! We kept seeing devs get pwned through MCP tools in ways that security scanners completely miss. So we built an open-source analyzer to catch these attacks. Our first OSS by Mighty team. The problem: At Defcon, we saw MCP exploits with 100% success rate against Claude and Llama. Three attack patterns: Hidden Unicode in "error messages" - Paste a colleague's error into Claude, your SSH keys get exfiltrated Trusted tool updates - That database tool you've used for months? Last week's update added credential theft Tool redefinition - Malicious tool redefines "deploy to prod" to run…

    2025 · github.com

  16. 16AO

    This is a small PoC Python project for web server access logs analyzing to classify and dynamically block bad bots, such as L7 (application-level) DDoS bots, web scrappers and so on. We'll be happy to gather initial feedback on usability and features, especialy from people having good or bad experience wit bots. *Requirements* The analyzer relies on 3 Tempesta FW specific features which you still can get with other HTTP servers or accelerators: 1. JA5 client fingerprinting (https://tempesta-tech.com/knowledge-base/Traffic-Filtering-b...). This is a HTTP and TLS layers…

    Oct 2025 · github.com

  17. 17

    Modern Python source code security analyzer.

    Jul 2026 · nocomplexity.com

  18. 18IB
  19. 19HA

    Hi HN, I'm one of the creators of HoundDog.ai (https://github.com/hounddogai/hounddog). We currently handle privacy scanning for Replit's 45M+ creators. We built HoundDog because privacy compliance is usually a choice between manual spreadsheets or reactive runtime scanning. While runtime tools are useful for monitoring, they only catch leaks after the code is live and the data has already moved. They can also miss code paths that aren't actively triggered in production. HoundDog traces sensitive data in code during development and helps catch risky flows (e.g., PII…

    Feb 2026 · github.com

  20. 20

    We're open-sourcing Sighthound today, our rules-based static security scanner. What makes it special is that it's coded in rust and uses tree-sitter as it's AST making it very fast and easily extensible. Why build another scanner in 2026? We wanted to improve some of our detection outcomes but noticed the current open source scanners like Semgrep/Opengrep we're capped by a bunch of adoption limitations such as being written in OCaml, requiring a lot of work to add a language parser, and the rulesets were licensed differently and required paid offerings. It also felt that licensing was…

    Jul 2026 · github.com

  21. 21KD

    I built this after seeing multiple teams accidentally ship API keys in their frontend code. The problem: Modern web development moves fast. You're vibe-coding, shipping features, and suddenly your AWS keys are sitting in a tag visible to anyone who opens DevTools. I've personally witnessed this happen to at least 3-4 production apps in the past year alone. KeyLeak Detector runs through your site (headless browser + network interception) and checks for 50+ types of leaked secrets: AWS/Google keys, Stripe tokens, database connection strings, LLM API keys (OpenAI, Claude, etc.), JWT…

    Nov 2025 · github.com

  22. 22IB

    I built a GitHub app that detects it in pull requests, notifies or blocks them. Alongside it, I published a Semgrep ruleset for any stage of the CI/CD. I started this after getting frustrated by all the FUD around malicious code - lots of noise, little effort to solve it. Having said that, it's still a major attack vector - a stored RCE, with the codebase itself as the sink. Feedback is appreciated. The app, PRevent - https://github.com/apiiro/PRevent The ruleset: https://github.com/apiiro/malicious-code-ruleset The research:…

    2025 · github.com

  23. 23OO
  24. 24DC

Ranked by how close each launch is in meaning, then by votes. Refine with a description →