sourcegraph-public-snapshot

sourcegraph/sourcegraph-public-snapshot

Code AI platform with Code Search & Cody

Ship status

Gone silent
Last push
Sep 2, 2024
760 days ago
Stars, last 7 weeks
Stars, weekly: 10,296 → 10,299 (Aug 18 – Sep 29, 2026)
+1 stars in the 28 days to 2026-09-29

GitHub reports this repository as archived. That forces the status to silent whatever the last push says.

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
10.3K
Forks
1.4K
Open issues
4.7K
Watchers
17
Primary language
Go
License
Other
Created
Aug 24, 2015
Owner
sourcegraph · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 99 startups in the directory ship primarily in Go.

Topics

#code-intelligence#code-search#cody#repo-type-main#sourcegraph

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 96%, self-hostable 39%, hosted offering 91%. 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.

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: silent — last push 2024-09-02This is the badge for sourcegraph/sourcegraph-public-snapshot, as served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/sourcegraph/sourcegraph-public-snapshot.svg)](https://ossean.com/sourcegraph/sourcegraph-public-snapshot)

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.