REPOGEO REPORT · LITE

max0x7ba/atomic_queue

Default branch master · commit 705fe1ac · scanned 5/20/2026, 5:13:00 AM

GitHub: 1,852 stars · 217 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE

40 /100

Critical

Category recall

0 / 2

Not recommended in any query

Rule findings

2 pass · 0 warn · 0 fail

Objective metadata checks

AI knows your name

3 / 3

Direct prompts that named your repo

HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface max0x7ba/atomic_queue, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION

highreadme#1

Reposition the README's opening to explicitly state its core value proposition and key differentiators

Why:

CURRENT

# atomic_queue
C++14 multiple-producer-multiple-consumer *lock-free* queues based on circular buffers and [`std::atomic`][3].

COPY-PASTE FIX

# atomic_queue: High-Performance C++14 Lock-Free & Wait-Free Queues

atomic_queue provides highly optimized, header-only, wait-free (for SPSC) and lock-free (for MPMC) concurrent queues, designed for predictable, ultra-low-latency inter-thread communication in C++14 applications.

mediumabout#2
Enhance the repository description to explicitly mention it's a 'library'
Why:
CURRENT
```
C++14 concurrent lock-free low-latency queue.
```
COPY-PASTE FIX
```
Header-only C++14 library for concurrent lock-free, low-latency queues.
```

lowreadme#3

Add a concise 'Key Features' section to the README

Why:

COPY-PASTE FIX

## Key Features

- Header-only C++14 library
- Wait-free Single-Producer-Single-Consumer (SPSC) queues
- Lock-free Multiple-Producer-Multiple-Consumer (MPMC) queues
- Designed for ultra-low latency and high throughput
- Based on circular buffers and `std::atomic`
- Extensively benchmarked on Linux, tested on x86_64, arm64, Ubuntu, and Windows.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall

0 / 2

0% of queries surface max0x7ba/atomic_queue

Avg rank

—

Lower is better. #1 = top recommendation.

Share of voice

Of all named tools, what % are you?

Top rival

cameron314/concurrentqueue

Recommended in 1 of 2 queries

COMPETITOR LEADERBOARD

cameron314/concurrentqueue · recommended 1×
facebook/folly · recommended 1×
boost::lockfree::queue · recommended 1×
david-levy/concurrencpp · recommended 1×
Boost.Lockfree · recommended 1×

CATEGORY QUERY
Looking for a C++ lock-free queue for high-performance, low-latency multi-threaded applications.
you: not recommended
AI recommended (in order):
1. moodycamel::ConcurrentQueue (cameron314/concurrentqueue)
2. folly::MPMCQueue (facebook/folly)
3. boost::lockfree::queue
4. concurrencpp::concurrent_queue (david-levy/concurrencpp)
AI recommended 4 alternatives but never named max0x7ba/atomic_queue. This is the gap to close.
Show full AI answer
CATEGORY QUERY
What are efficient C++ atomic queue implementations using circular buffers for inter-thread communication?
you: not recommended
AI recommended (in order):
1. Boost.Lockfree
2. folly::MPMCQueue
3. moodycamel::ConcurrentQueue
4. concurrencpp
5. std::atomic based custom implementation
6. readerwriterqueue
AI recommended 6 alternatives but never named max0x7ba/atomic_queue. This is the gap to close.
Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

Metadata completeness
pass
README presence
pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

Compared to common alternatives in this category, what is the core differentiator of max0x7ba/atomic_queue?
pass
AI named max0x7ba/atomic_queue explicitly
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
If a team adopts max0x7ba/atomic_queue in production, what risks or prerequisites should they evaluate first?
pass
AI named max0x7ba/atomic_queue explicitly
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?
In one sentence, what problem does the repo max0x7ba/atomic_queue solve, and who is the primary audience?
pass
AI named max0x7ba/atomic_queue explicitly
AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of max0x7ba/atomic_queue. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

Live preview

MARKDOWN (README)

[![RepoGEO](https://repogeo.com/badge/max0x7ba/atomic_queue.svg)](https://repogeo.com/en/r/max0x7ba/atomic_queue)

HTML

<a href="https://repogeo.com/en/r/max0x7ba/atomic_queue"><img src="https://repogeo.com/badge/max0x7ba/atomic_queue.svg" alt="RepoGEO" /></a>

Pro

Subscribe to Pro for deep diagnoses

max0x7ba/atomic_queue — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

Deep reports10 / month
Brand-free category queries5 vs 2 in Lite
Prioritized action items8 vs 3 in Lite