Vane

ItzCrazyKns/Perplexica · now at ItzCrazyKns/Vane

Vane is an AI-powered answering engine.

Ship status

Slowed

Last push 31–120 days ago. Quiet, not gone.

Last push
Sep 1, 2026
59 days ago
Ship score
36/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 36,794 → 37,766 (Sep 15 – Oct 27, 2026)
+840 stars in the 28 days to 2026-10-27

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

Repo facts

What GitHub reports.

Stars
37.9K
Forks
4.2K
Open issues
368
Watchers
208
Primary language
TypeScript
Created
Apr 9, 2024
Owner
ItzCrazyKns · User

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. 210 startups in the directory ship primarily in TypeScript.

Topics

#ai-agents#ai-search-engine#answering-engine#artificial-intelligence#llm#machine-learning#open-source-ai-search-engine#perplexica#rag#search-engine#searxng#searxng-copilot#self-hosted-ai#vane

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose something else instead, and put os_startup at 29% (self-hostable 45%, hosted offering 23%). 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. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: slowed — last push 2026-09-01This is the badge for ItzCrazyKns/Perplexica, as served from the URL below.
[![OSSEAN: slowed](https://ossean.com/badge/ItzCrazyKns/Perplexica.svg)](https://ossean.com/ItzCrazyKns/Perplexica)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.