Skip to content

Github · GitHub Repository Radar

hackerai-tech hackerai

Find and fix vulnerabilities by chatting with AI

Stars

659

Active Stable

Forks

165

Watchers: 659

Repository Radar Score

54 / 100

Growth

7d
+0
30d
+0
%
0.0%

Not enough metric snapshots yet to chart growth for this repository.

Score breakdown

  • popularity 52
  • growth 0
  • activity 100
  • freshness 100
  • community 85

Need help integrating this stack?

Our team builds with modern open-source stacks. Tell us what you are shipping.

Get a quote →

HackerAI Logo

HackerAI

Your AI-Powered Penetration Testing Assistant

Getting started

Prerequisites

You'll need the following accounts:

Required:

  • OpenRouter - AI model provider
  • OpenAI - Content moderation
  • E2B - Isolated cloud execution in Agent mode
  • Convex - Database and backend
  • WorkOS - Authentication and user management
  • Trigger.dev - Required durable runtime for agent tasks

Optional:

Clone the repo

git clone https://github.com/hackerai-tech/hackerai.git

Navigate to the project directory

cd hackerai

Install dependencies

pnpm install

Run the setup script

pnpm run setup

Start the development server

This runs both Next.js and Convex dev servers:

pnpm run dev

Or run them separately in two terminals:

pnpm run dev:next
pnpm run dev:convex

Run the Trigger.dev worker

Agent mode runs the agent loop on a Trigger.dev task. To use the agent locally:

  1. Create a project at https://cloud.trigger.dev and copy your dev secret key (tr_dev_…) into .env.local as TRIGGER_SECRET_KEY.

  2. In the Trigger.dev dashboard → your project → Environment Variables, add the env vars the task needs to run (these live on the worker, not on Vercel): NEXT_PUBLIC_CONVEX_URL, CONVEX_SERVICE_ROLE_KEY, OPENROUTER_API_KEY, OPENAI_API_KEY, one cloud sandbox provider, plus any keys you use (PERPLEXITY_API_KEY, JINA_API_KEY, S3, etc.).

  3. Start the worker in a third terminal:

    pnpm dev:trigger

    This starts the default Trigger.dev worker used by local Agent requests. To start an explicitly routed Trigger.dev branch instead, set a stable branch name with TRIGGER_DEV_BRANCH=my-local-agent pnpm dev:trigger. Only use that override when the request path is configured to target the same Trigger.dev branch.

Created: Aug 9, 2025

Last push: Sep 3, 2026

Default branch: main

Latest release: desktop-v0.0.59

Languages

Share of the codebase by language, based on repository metadata from the host.

  • TypeScript 98.1%
  • Rust 0.9%
  • JavaScript 0.6%
  • Dockerfile 0.2%
  • CSS 0.1%
  • HTML 0.0%
  • Shell 0.0%

Repository Radar analysis

Deterministic insights derived from public metadata and our observations — not personal testing or reviews.

Why this repository is interesting

  • Maintained recently (last push 2 weeks ago).

Who should use it

  • Developers working primarily with TypeScript
  • Teams exploring AI tooling, agents, or ML infrastructure
  • Frontend engineers comparing UI frameworks and tools

Potential use cases

  • Reference or evaluate TypeScript open-source approaches in this domain
  • Prototype AI/agent workflows or study reference architectures

Strengths

  • Recent repository activity
  • README present in our index
  • Declared license: Other

Limitations / considerations

  • Insights are derived from public metadata and our observations — not a substitute for code review

What to watch

  • Re-check last push, issues, and releases on GitHub before production adoption

Strong signals: Active maintenance

Source: GitHub (public metadata) + Repository Radar analysis. We do not claim ownership of third-party repositories.

Ready to ship something that compounds?

Share your roadmap. We’ll come back with scope options, timeline ranges, and who from Shriram IT Ventures should be in the room.

Popular with product teams