ChessPivot
free opening repertoire scanner

Opening Scanner review: scores and evidence

Opening Scanner reads up to 2,000 Lichess/Chess.com or PGN games in the browser and shows the real repertoire, scores per opening, weak spots and a PGN export. It has no engine, no exercises and no account.

Read on August 30, 2026 from the service’s public pages — every score cites the page read.

Overall score

3.0/ 10

Rank

38/ 128

Languages

13

Listed price

€0 (free, no account needed — openingscanner.com, MIT README).

Official site
01

What the service is

Opening Scanner is an open-source web tool released under the MIT licence by an independent developer, "Antoine" (GitHub handle atamano), whose profile lists France and the IndieFoundry label; no publishing company is named on the site itself. The GitHub repository was created on 17 April 2026 (first commit "add opening tracker" on that date, commits page), and the site links to two sister sites, chessatlas.net and chessendings.com. The service reads up to 2,000 games from a Lichess or Chess.com username, or from a PGN file, entirely in the browser with no account and no server; it classifies openings against Lichess’s chess-openings database (full ECO catalogue), shows the player’s real repertoire by family and variation with win/draw/loss scores and average opponent rating, flags weak spots and coverage gaps, and exports a filtered PGN or a study-ready repertoire. Filter state lives in the URL, which makes a scan shareable, and the interface is available in 13 languages including French. Everything is free, with no sign-up and no paid tier. The tool ships no analysis engine, offers no exercises, courses, play or tracking over time, and the repository publishes neither releases nor a changelog.

02

Activity history

  1. 2026-0712 July 2026: latest commits on the main branch — dependency update (16 Dependabot advisories), hreflang fix and chessendings.com added to the sister sites.
  2. 2026-0511 May 2026: a sample-size confidence badge is added to win-rate displays.
  3. 2026-0510 May 2026: series of SEO fixes (canonicals and sitemap on the www host, server-rendered footer).
  4. 2026-0417 April 2026: creation of the GitHub repository atamano/openingscanner and first commit "add opening tracker".
03

The scores, evidence by evidence

Every score points to the page read and the fact found there. A fact documented nowhere is not credited: document it, then write to us.

APersonalized diagnosis

1.7

A1 :3Importing your games (Chess.com, Lichess, PGN files)

https://github.com/atamano/openingscanner — Lichess + Chess.com (API) + PGN files, 2,000 games

A2 :0Automatic engine analysis of every game

https://github.com/atamano/openingscanner — no engine

A3 :1Recurring mistakes identified across all your games

https://github.com/atamano/openingscanner: "weak spots" = lowest-scoring openings; no error named

A4 :0Types of mistakes covered (tactics, strategy, endgame, time…)

https://github.com/atamano/openingscanner: no error typology

A5 :0Written explanation of each mistake

https://github.com/atamano/openingscanner: W/D/L figures only

A6 :0Stated verification of the diagnoses (procedure, rates)

https://github.com/atamano/openingscanner — no mention

A7 :0Tracking each weakness over time

https://github.com/atamano/openingscanner — no history

A8 :0Comparison with players of the same rating

https://github.com/atamano/openingscanner — average opponent rating, no percentile

BOpenings

1.7

B1 :1Building a personal repertoire

https://github.com/atamano/openingscanner — "study-ready repertoire PGN" export generated from one’s games; no editor

B2 :0Training the repertoire (drills, games)

https://openingscanner.com/ — no drill

B3 :1Spotting where you left your repertoire in your games

https://github.com/atamano/openingscanner — W/D/L by opening and coverage "gaps"; no reference repertoire

B4 :0Verification of the lines taught (engine, practice)

https://github.com/atamano/openingscanner — no line taught

B5 :1Opening explorer and statistics

https://github.com/atamano/openingscanner — explorer of one’s own games only

B6 :0Explanation of opening plans and ideas

https://openingscanner.com/ — none

CTargeted training

0.0

C1 :0Exercises drawn from your own games

https://openingscanner.com/ — no exercises

C2 :0Bank of tactical exercises (size, themes, rating)

https://openingscanner.com/ — none

C3 :0Endgame training

https://openingscanner.com/ — nothing

C4 :0Strategic and positional training

https://openingscanner.com/: nothing

C5 :0Training defense and alertness

https://openingscanner.com/: nothing

C6 :0Training calculation and visualization

https://openingscanner.com/ — nothing

C7 :0Difficulty matched to your real level

https://openingscanner.com/ — no exercises

C8 :0Spaced repetition (named algorithm)

https://openingscanner.com/: none

C9 :0Personalized training plan

https://openingscanner.com/: none

DPrice and value

10.0

D1 :3What the free plan actually lets you do

https://openingscanner.com/ — "Free chess opening scanner", no account

D2 :3Annual price of the full plan

https://openingscanner.com/ — €0

D3 :3Commercial transparency (price shown, trial, cancellation)

https://openingscanner.com/ — free, no sign-up

D4 :3Number of paid tiers (how simple the offer is)

https://github.com/atamano/openingscanner: free, MIT licence, no account

EEvidence and transparency

5.8

E1 :0Published evidence of effectiveness

https://openingscanner.com/ — no data

E2 :1Chess verification of the content (positions, lines)

https://github.com/atamano/openingscanner — classification based on the lichess chess-openings database; fixes via GitHub issues

E3 :3Transparency of the method (algorithms, code)

https://github.com/atamano/openingscanner — MIT code, architecture described

E4 :3Marketing claims that can be checked (no overselling)

https://github.com/atamano/openingscanner — factual; limit stated (2,000 games, 100% browser)

FContent and method

1.3

F1 :0Courses organized by rating level

https://openingscanner.com/ — no courses

F2 :0Course authors named and titled

https://openingscanner.com/ — none

F3 :0Content formats (text, video, interactive)

https://openingscanner.com/ — no content

F4 :0Published method of progression

https://openingscanner.com/ — none

F5 :2How often the content is updated

https://api.github.com/repos/atamano/openingscanner — pushed_at 2026-08-24 (< 3 months); no monthly changelog

GPlaying and practice

0.0

G1 :0Playing humans online (pool, anti-cheating)

https://openingscanner.com/ — no play

G2 :0Realistic artificial opponents

https://openingscanner.com/ — none

G3 :0Replaying one specific position against the machine

https://openingscanner.com/ — none

G4 :0Tournaments and organized competition

https://openingscanner.com/ — none

HExperience and accessibility

2.7

H1 :1Platforms available (web, iOS, Android, desktop)

https://openingscanner.com/ — web only

H2 :0User ratings and reviews (stores, press)

https://openingscanner.com/ — no store rating or third-party review

H3 :2Interface languages available

13 interface languages observed — https://openingscanner.com/ — 13 languages including French (interface); no teaching content

H4 :0Accessibility (keyboard, screen reader)

https://openingscanner.com/ — no mention

H5 :1Offline use and known incidents

https://github.com/atamano/openingscanner — 100% client-side, IndexedDB cache, but depends on the Lichess/Chess.com APIs

IPreparation and study

3.3

I1 :2Preparing for a named opponent

https://github.com/atamano/openingscanner: scan of any Lichess/Chess.com username, repertoire by family, "per-position results (W/D/L, avg opponent ELO)"

I2 :0Annotating and sharing games (studies)

https://openingscanner.com/: no annotation

I3 :0Entering a game played at a club (photo, scoresheet)

https://openingscanner.com/: no board entry

I4 :2Searching your games (filters, position)

https://github.com/atamano/openingscanner: "filter state" in the URL, navigation by opening/variation, PGN "filtered to the current variation"

JHuman coaching and community

1.7

J1 :0Access to human coaches

https://openingscanner.com/ — none

J2 :0Size and activity of the community

https://github.com/atamano/openingscanner — 14 stars, no community

J3 :0Tools for trainers, clubs and schools

https://openingscanner.com/ — none

J4 :2Engagement mechanics (streaks, virtual currency, reminders)

https://openingscanner.com/ — no gamification and no pressure

KPersonal data and interoperability

7.8

K1 :2Exporting your data (games, repertoire)

https://github.com/atamano/openingscanner — filtered PGN export and repertoire PGN

K2 :2Protection of personal data (GDPR, hosting)

https://github.com/atamano/openingscanner — no server, no data collected ("no backend"); no formal policy

K3 :3Public API and source code

https://api.github.com/repos/atamano/openingscanner — MIT licence

04

Also, outside the grid

Features found that no criterion measures. They do not count towards the score.

  • PGN export of a repertoire with nested variations
  • Gap analysis against curated openings
  • Scan shareable by URL, 13 languages
06

Sources consulted

07

Services with a similar profile

The three services whose category profile is closest — a distance over the eleven scores, computed, never chosen.