Report · marked 26 Aug 2026
apache/echarts
Solid foundations, held back in a few specific places.
TypeScript · 67,149 stars · 2,182 files · branch master
80
/100
A-
Instructions
25/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup
12/14Whether an agent can install the project and get it running without a human. Losing marks on pinned runtime version.Verification loop
21/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on lint and format rules and static type checking.Context economy
11/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability
8/10How quickly anything new can orient itself. Losing marks on written documentation.
Higher is better. Accent marks what is costing you most.
Fix these first
01
File sizes fit in context
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
02
Lint and format rules
A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.
03
Repository weight
Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.
The full marking
Every deduction below names the file or setting it came from.
Instructions 25/27 A+
Whether the repo tells an agent how to behave before it starts guessing.
✓Agent instruction file
12/12
AGENTS.md is present, which is the format the most tools read.
✗Instruction quality
10/12
Specific enough that an agent can act on it.
Worth fixing: has no code blocks.
4,544 characters, a workable length
names the actual commands to run
uses headings, so an agent can skim it
✓README as an entry point
3/3
README has a clear getting-started section.
Setup 12/14 A
Whether an agent can install the project and get it running without a human.
✓Deterministic install
6/6
package-lock.json pins the dependency tree.
Found package-lock.json
✓Discoverable commands
6/6
Commands are declared where an agent will look for them.
package.json scripts (build, build:esm, build:i18n, build:lib, build:extension, build:ssr…)
–Environment config
n/a
Not applicable — this reads as a library, with no environment to configure.
✗Pinned runtime version
0/2
No pinned runtime version.
Add a .nvmrc, .python-version, or equivalent so the agent's toolchain matches yours.
–Reproducible environment
n/a
Not applicable — a library doesn't need a container to be worked on.
Verification loop 21/25 A-
Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.
✓Tests exist
8/8
1374 test files against 868 source files.
e.g. test/-cases.html, test/-cases.js, test/README.md
✓Test command is discoverable
7/7
An agent can find and run `npm run test`.
✓Continuous integration
4/4
6 GitHub Actions workflows define what "passing" means.
✗Lint and format rules
0/3
No linter or formatter config. Style is tribal knowledge, so agent output will drift from yours.
A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.
✗Static type checking
2/3
Type checking is configured, but not in strict mode.
Turn on `"strict": true`. Type errors are the fastest feedback an agent gets, and non-strict mode silently discards most of them.
Context economy 11/20 B-
Whether the repo fits in a context window, or fights it.
✓No committed build output
6/6
No generated directories committed.
✓.gitignore hygiene
3/3
.gitignore covers 136 patterns.
✗File sizes fit in context
0/6
13 source files are over 100KB.
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
dist/echarts.js — 3757KB
dist/echarts.esm.mjs — 3384KB
dist/echarts.esm.js — 3384KB
✗Repository weight
2/5
About 271MB checked out. Large enough that cloning and searching are both slow.
Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.
Here is your AGENTS.md
Drafted from what is actually in this repository: the install
command from your lockfile, the commands you already declare, your real directory layout. Anything
marked TODO needs a person. Save it at the root as AGENTS.md.
# AGENTS.md Apache ECharts is a powerful, interactive charting and data visualization library for browser ## Setup ``` npm ci ``` ## Commands ``` npm run dev # run locally npm run build # produce a build npm run test # run the test suite, must pass before any commit npm run lint # lint npm run build:esm npm run build:i18n npm run build:lib npm run build:extension ``` ## Layout - `src/` 596 source files - `test/` 128 source files - `i18n/` 54 source files - `theme/` 43 source files - `build/` 29 source files - `dist/` 8 source files ## Conventions - Tests live alongside the code they cover, following `test/-cases.html`. - TypeScript is not in strict mode. Turning it on catches a whole class of mistakes before they run. - CI defines what passing means. See `.github/workflows/ci.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - Generated output is committed (`build/`). Search will return the compiled copy, so edit the source, not that. - `dist/echarts.js` is 3757KB. It will not fit comfortably in context, so read it in parts. --- Drafted by agentreadme.com from what is in this repository. Everything marked TODO needs a human. Check it in as AGENTS.md at the root.
Open the raw markdown
or
curl -o AGENTS.md agentreadme.com/draft/apache/echarts.md
Show the mark
The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.
[](https://agentreadme.com/apache/echarts)Other TypeScript repositories, marked
Think this mark is wrong?
Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.