Open-source project
SnosMe/awakened-poe-trade avatar
SnosMe/awakened-poe-trade

Awakened PoE Trade is an overlay that reads prices from three outside services, and its README is 46 words

:heavy_dollar_sign: :hammer: Path of Exile app for price checking

2,624 stars773 forksTypeScriptMIT

At a glance

What is it?
Awakened PoE Trade is a TypeScript desktop overlay for Path of Exile that shows what an item is worth while the game is running. The prices are not in the game and not in this repository either, they come from three acknowledged third-party services. What the README does not contain is any statement about rules, permissions or how much of the game the app touches.
Who is it for?
Its architecture is simple enough to read in an afternoon, and the honest summary is that it is an overlay built on public price data rather than a trading client. Treat it as code to study rather than something to run against a live account: nothing in the repository addresses the game's rules on third-party software, so that check is yours to make first, and if you do run it, understand that it hooks keyboard input and reads the running game.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 52 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • SnosMe/awakened-poe-trade2,624 ★ · +39
Star history
Repository2026-09-292026-11-15
SnosMe/awakened-poe-trade2.6k2.6k

39 Stars in the last 47 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

It runs beside the game and hooks the keyboard, and the repository says nothing about permission

Start with the part that is not in the documentation. This is companion software for Path of Exile that is meant to be present while the game is running, and one of its four acknowledged dependencies is libuiohook, a library for hooking keyboard and mouse input system wide. Software that reads game state and watches input on the same machine as a live game is the category that online games tend to regulate in their own terms, and this repository contains no statement about those terms. There is no note about permission from the publisher, no discussion of anti cheat behaviour, no description of what happens when the game updates its memory layout, and no explanation of how the app identifies the game process. That absence is worth taking at face value: nothing here tells you the project has been cleared for use with a live account, and the decision about whether to run it belongs to the person holding the account.

Prices are fetched from outside the game, so the app is an aggregator

The acknowledgments settle the most important architectural question. Three of the four credited projects are data sources rather than code the app builds on: RePoE, which holds Path of Exile item data, and two price services, poeprices.info and poe.ninja. So the item metadata comes from one place, the values come from two others, and the overlay's job is to join them, watch what you have under the cursor, and draw the result over the game window. Nothing about that arrangement requires the game to send prices anywhere, which is also why the app's output can be stale or absent: if a service changes its interface or rate limits, the overlay has nothing to show and no local fallback is described. Two further design questions are left open by that dependency list. It does not say how two independent price services are reconciled when they disagree, and it does not say whether the overlay shows a currency conversion, a league specific value, or both. The fourth credit, libuiohook, is the only dependency that touches your machine directly rather than the network.

The tree is a three-part desktop layout with a development file that is not in the README

The repository is laid out as a desktop application split into three directories: main, renderer and ipc. That is the shape you get when interface code is kept apart from the process that owns the window, with ipc holding what the two exchange, and it matches the two facts the project does advertise, a TypeScript language tag and a workspace file named awakened-poe-trade.code-workspace for opening the tree in an editor. Alongside those sit a docs directory and a file called DEVELOPING.md, which the README points to as its single development reference. None of that file's contents appear in the README itself, so the build steps, the scripts and the release process are all outside what this repository's front page gives you. There is no source for the game interaction layer to read either, since the libuiohook side of the architecture lives in code the acknowledgments name rather than in code this tree documents. The docs directory is present but unreferenced, so whatever is in it is left for a reader to discover by browsing rather than by following a link.

crowdin.yml means the interface text is managed outside the repository

A crowdin.yml sits at the root next to the README and the licence file, and Crowdin is a translation management service, so the interface strings are handled somewhere other than in this tree. That matters for anyone who wants to change wording, add a language or follow a bug that mentions a label: the source strings are not obviously here, and a translator working through the service would be editing a copy rather than the repository. The README itself is a single English page with no translation links and no contributing section beyond the badge row, so a project with 2586 stars and 759 forks has its localisation arranged through the file rather than described anywhere a newcomer would read. The remaining root entries are conventional: a gitignore, a GitHub directory for templates and workflows, and the MIT licence file.

The one table in the README has four headers and no rows

Under a tool heading the README prints a four column table headed Gem, Rare, Unique and Currency, and then a single empty row. The screenshots that would fill those four cells are not in the file, which is the only illustration a reader gets. Given a 46 word README, this is the single largest gap in it: there is no description of what the overlay looks like, no screenshot of it over the game, no settings list, no hotkey reference, and no statement of which game versions or leagues it supports. Those omissions are normal for a project whose users arrive from its download page rather than from its repository, but they mean the repository itself documents almost nothing about the product. What it does document well is the dependency set and the release cadence. The four column headings are also the whole of the stated feature surface, since nothing else in the file says what the app can display.

Three releases in four weeks, all on the same minor version

The release record shows v3.29.106 published on 2026-08-16, v3.29.107 on 2026-08-18 and v3.29.108 on 2026-09-09, with the last push to the repository dated 2026-09-24 and no archived flag. So the cadence is measured in days rather than months, two of those three releases two days apart, and every one of them sits on the same 3.29 minor with only the patch number moving. Each release name repeats its own tag rather than carrying notes, so the change log is not in the release entries either. A release statistics badge in the README points at a third party's service with this repository's owner and name passed as parameters, which is where a reader would look for release history beyond the three entries above. The default branch is master, and no topics are declared on the repository. The issue tracker is where the cadence becomes visible too, with 351 open issues against those 2586 stars and 759 forks. For an overlay that follows a game through frequent updates, that backlog is the honest measure of what this project is: a small team shipping patches several times a month and answering questions afterwards.

The download page is the homepage, and it names two operating systems

The repository's homepage field and the one prominent link in the README are the same address, a download page under the project's own GitHub Pages site, and the surrounding text names Windows and Linux. That is the entire distribution story the README gives: a link, two platforms, and no install command anywhere. Windows gets a specific mention nowhere beyond that word, and no build is described for macOS, so the platform coverage is what one sentence says and no more. Because the link is the homepage field, the repository has no separate landing page of its own, which is consistent with a project whose front door is the installer rather than the source. The README also opens with three badges, for release statistics, a Patreon page and an issue, none of which describe the application itself.

Editorial conclusion

Its architecture is simple enough to read in an afternoon, and the honest summary is that it is an overlay built on public price data rather than a trading client. Treat it as code to study rather than something to run against a live account: nothing in the repository addresses the game's rules on third-party software, so that check is yours to make first, and if you do run it, understand that it hooks keyboard input and reads the running game.

Frequently asked questions

What is Awakened PoE Trade?

A TypeScript desktop overlay for Path of Exile that shows what an item is worth while the game is running. It is MIT licensed and its repository is laid out as main, renderer and ipc directories.

Where does Awakened PoE Trade get item prices?

From outside the game. The README acknowledges RePoE for item data and two price services, poeprices.info and poe.ninja, and a fourth credit, libuiohook, for hooking keyboard and mouse input on the machine.

Is Awakened PoE Trade allowed with Path of Exile?

The repository does not address it. There is no statement about the game's rules on third-party software, no mention of permission from the publisher, and no note about anti cheat behaviour, so that has to be checked against the game's own terms before use with a live account.

Which operating systems does Awakened PoE Trade build for?

The README names Windows and Linux, and the download page it links is also the repository homepage. No macOS build is mentioned anywhere in the README.

Is Awakened PoE Trade still being updated?

The release list shows v3.29.106, v3.29.107 and v3.29.108 published between 2026-08-16 and 2026-09-09, and the last push is dated 2026-09-24 with the repository not archived.

How do I set up a development environment for Awakened PoE Trade?

The README gives no build steps at all. It points at a file called DEVELOPING.md in the repository root and at a workspace file for opening the tree in an editor, and that is the whole of its development guidance.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. SnosMe/awakened-poe-trade on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/snosme-awakened-poe-trade.svg)](https://hysenlabs.com/projects/snosme-awakened-poe-trade)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/snosme-awakened-poe-trade.svg)](https://hysenlabs.com/projects/snosme-awakened-poe-trade)

Was this useful?