faraday

infobyte/faraday

Open-source and AI-powered cybersecurity tools for offensive security, vulnerability management, and autonomous pentesting. Built by hackers in Latin America, used worldwide.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
29 Oct 2026
21 days ago
Ship score
60/100
How it is calculated →
Stars, last 7 weeks
no history yet
No weekly sample has been taken for this repository yet.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repository facts

Stars
6.9K
Forks
1.1K
Open issues
16
Watchers
242
Primary language
Python
Created
6 Nov 2013
Owner
infobyte · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 141 startups in the directory ship primarily in Python.

Topics

#appsec#autonomous-agents#autonomous-pentest#collaboration#continuous-scanning#cve#cybersecurity#devops#devsecops#infosec#llm#orchestration#penetration-testing#pentesting#security#security-audit#security-automation#vulnerability#vulnerability-management#vulnerability-scanners

How Jev classified this project

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 19 Nov 2026 — os_startup 95%, self-hostable 67%, hosted offering 67%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 19 Nov 2026, found by the weekly discovery job at confidence 0.93. Answered by jev-1.14.0. How the classification works →

Add the status badge to your README

OSSEAN ship status: shipping — last push 29 Oct 2026This is the badge for infobyte/faraday, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/infobyte/faraday.svg)](https://ossean.com/infobyte/faraday)

Updates daily, from the last push GitHub saw.

The badge links to this profile, even after a GitHub rename. GitHub caches README images, so the badge can take a little longer to update there.