Report · marked 25 Aug 2026
oven-sh/bun
An agent can work here, but it will waste turns finding its footing.
Rust · 95,684 stars · 19,650 files · branch main
68
/100
B
Instructions
15/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup
16/18Whether an agent can install the project and get it running without a human. Losing marks on environment config.Verification loop
24/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on static type checking.Context economy
6/20Whether the repo fits in a context window, or fights it. Losing marks on no committed build output and file sizes fit in context.Navigability
7/10How quickly anything new can orient itself. Losing marks on license.
Higher is better. Accent marks what is costing you most.
Fix these first
01
Instruction quality
Worth fixing: it's under 200 characters, which is closer to a placeholder than instructions; it never states a build, test, or run command; has no headings to structure it; has no code blocks.
02
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.
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 15/27 B-
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.
Also found: CLAUDE.md
✗Instruction quality
0/12
Present but too thin to change an agent's behavior.
Worth fixing: it's under 200 characters, which is closer to a placeholder than instructions; it never states a build, test, or run command; has no headings to structure it; has no code blocks.
✓README as an entry point
3/3
README has a clear getting-started section.
Setup 16/18 A
Whether an agent can install the project and get it running without a human.
✓Deterministic install
6/6
bun.lock pins the dependency tree.
Found bun.lock
✓Discoverable commands
6/6
Commands are declared where an agent will look for them.
package.json scripts (build, ci:find, ci:status, ci:errors, ci:logs, ci:watch…)
scripts/ directory
✗Environment config
2/4
Env vars are mentioned in the README but there's no example file to copy.
Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.
✓Pinned runtime version
2/2
The language runtime version is pinned.
Found rust-toolchain.toml
–Reproducible environment
n/a
Not applicable — a library doesn't need a container to be worked on.
Verification loop 24/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
14870 test files against 14063 source files.
e.g. bench/expect-to-equal/expect-to-equal.test.js, bench/expect-to-equal/expect-to-equal.vitest.test.js, bench/stress/hot-reload-files/run-stress-test.sh
✓Test command is discoverable
7/7
An agent can find and run `npm run test`.
✓Continuous integration
4/4
31 GitHub Actions workflows define what "passing" means.
✓Lint and format rules
3/3
clippy.toml encodes the house style.
✗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 6/20 D
Whether the repo fits in a context window, or fights it.
✗No committed build output
3/6
Generated output is committed: node_modules/.
Add these to .gitignore and `git rm -r --cached` them. Generated files pollute search results, so an agent grepping for a function finds the compiled copy and edits the wrong file.
✓.gitignore hygiene
3/3
.gitignore covers 196 patterns.
✗File sizes fit in context
0/6
161 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.
src/jsc/bindings/sqlite/sqlite3.c — 9285KB
test/bundler/transpiler/fixtures/lots-of-for-loop.js — 8828KB
test/js/node/test/fixtures/snapshot/typescript.js — 2268KB
✗Repository weight
0/5
About 960MB 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 Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one ## Setup ``` bun install ``` ## Commands ``` bun build # produce a build bun test # run the test suite, must pass before any commit bun typecheck # type check without emitting bun lint # lint bun ci:find bun ci:status bun ci:errors bun ci:logs ``` ## Layout - `test/` 10310 source files - `src/` 3166 source files - `bench/` 303 source files - `packages/` 199 source files - `scripts/` 66 source files - `misctools/` 7 source files ## Conventions - Tests live alongside the code they cover, following `bench/expect-to-equal/expect-to-equal.test.js`. - 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/auto-assign-types.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - `src/jsc/bindings/sqlite/sqlite3.c` is 9285KB. 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/oven-sh/bun.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/oven-sh/bun)Other Rust 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.