ProjectDiscovery
project-discovery · C · candidate
https://projectdiscovery.io/blog/stories/1
ProjectDiscovery (Nuclei templates), exploit-scanner authors; strong on emerging-CVE PoCs and pre-disclosure scanning (added 2026-05-08). 2026-05-08 audit: WebFetch returned 5 blog titles; per-post dates not surfaced, drill into individual posts. Candidate; promote to active after 3 runs. | 2026-06-20 full audit (v2.62): live=Y, drill=Y. FETCH → webfetch (listing) https://projectdiscovery.io/blog then webfetch per-article /blog/{slug}.. AVOID: Per-post dates were thin on the listing in the original audit; current posts do carry dates on the article pages. Recent output is product/AI-agent focused; don't expect emerging-CVE PoCs every run.. | 2026-07-05 admiralty audit: C (MEDIUM->C) status candidate->candidate, tooling vendor with some original CVE/Nuclei research but product-marketing-heavy recent output; live/drillable but intel relevance genuinely unproven, so keep candidate rather than promote. | 2026-09-29: /blog is a featured/curated page (newest visible card July 21, 2026) - use https://projectdiscovery.io/blog/stories/1 (chronological, dated "Month D, YYYY" cards, paginated /blog/stories/N) with `url` (raw; `extract` returns only the cookie banner), then `extract https://projectdiscovery.io/blog/<slug>` per post. Newest 2026-08-16; ~2 posts/month, mostly product/AI-agent (Neo) with occasional CVE research; max_staleness_days 75. The first `url --direct` GET can hit a transient TLS handshake timeout - retry once. (2026-09-29T2134Z-audit)
Cited in 0 entries
Not cited in any entry yet.