RRepoGEO

REPOGEO REPORT · LITE

JPCERTCC/LogonTracer

Default branch master · commit c97edf79 · scanned 5/14/2026, 7:17:08 PM

GitHub: 3,176 stars · 489 forks

AI VISIBILITY SCORE
35 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 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 JPCERTCC/LogonTracer, 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 emphasize specialized graph visualization

    Why:

    CURRENT
    **LogonTracer v2** is a tool to investigate malicious logon by visualizing and analyzing Windows Active Directory event logs. This tool associates a host name (or an IP address) and account name found in logon-related events and displays it as a graph.
    COPY-PASTE FIX
    **LogonTracer v2** is a specialized tool for investigating malicious Windows logon attempts by visualizing and analyzing Active Directory event logs using a graph database. It uniquely associates hostnames and account names from logon events, displaying them as an interactive graph to quickly uncover suspicious activity, offering a focused alternative to general SIEM platforms.
  • mediumhomepage#2
    Add a homepage URL to the repository's 'About' section

    Why:

    COPY-PASTE FIX
    Add a relevant project page, documentation site, or dedicated section on JPCERT/CC's website to the repository's 'About' section.
  • mediumlicense#3
    Clarify the existing license in the README

    Why:

    COPY-PASTE FIX
    Add a section or line in the README (e.g., under 'License' heading) that explicitly states the terms and conditions of the existing LICENSE file, or clarifies which license(s) apply.

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 JPCERTCC/LogonTracer
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Microsoft Sentinel
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Microsoft Sentinel · recommended 2×
  2. Splunk Enterprise Security · recommended 1×
  3. ELK Stack · recommended 1×
  4. Graylog · recommended 1×
  5. Event Log Explorer · recommended 1×
  • CATEGORY QUERY
    How can I visualize and analyze Windows event logs to investigate malicious logon attempts?
    you: not recommended
    AI recommended (in order):
    1. Splunk Enterprise Security
    2. ELK Stack
    3. Microsoft Sentinel
    4. Graylog
    5. Event Log Explorer
    6. PowerShell

    AI recommended 6 alternatives but never named JPCERTCC/LogonTracer. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Tool for visualizing Active Directory logon events to detect suspicious security activity.
    you: not recommended
    AI recommended (in order):
    1. Splunk Enterprise Security (ES)
    2. Microsoft Sentinel
    3. Elastic Security
    4. Exabeam Security Operations Platform
    5. Rapid7 InsightIDR
    6. LogRhythm SIEM

    AI recommended 6 alternatives but never named JPCERTCC/LogonTracer. This is the gap to close.

    Show full AI answer

Objective checks

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

  • Metadata completeness
    warn

    Suggestion:

  • 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 JPCERTCC/LogonTracer?
    pass
    AI named JPCERTCC/LogonTracer explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts JPCERTCC/LogonTracer in production, what risks or prerequisites should they evaluate first?
    pass
    AI named JPCERTCC/LogonTracer 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 JPCERTCC/LogonTracer solve, and who is the primary audience?
    pass
    AI named JPCERTCC/LogonTracer 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 JPCERTCC/LogonTracer. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/JPCERTCC/LogonTracer.svg)](https://repogeo.com/en/r/JPCERTCC/LogonTracer)
HTML
<a href="https://repogeo.com/en/r/JPCERTCC/LogonTracer"><img src="https://repogeo.com/badge/JPCERTCC/LogonTracer.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

JPCERTCC/LogonTracer — 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