Report · marked 25 Aug 2026
nextcloud/server
Solid foundations, held back in a few specific places.
PHP · 36,578 stars · 12,911 files · branch master
83
/100
A-
Instructions
23/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup
16/16Whether an agent can install the project and get it running without a human. Full marks.Verification loop
25/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Full marks.Context economy
9/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
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.
03
Instruction quality
Worth fixing: it never states a build, test, or run command.
The full marking
Every deduction below names the file or setting it came from.
Instructions 23/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.
Also found: CLAUDE.md
✗Instruction quality
8/12
Real instructions, with gaps.
Worth fixing: it never states a build, test, or run command.
8,342 characters, a workable length
uses headings, so an agent can skim it
includes copyable code blocks
✓README as an entry point
3/3
README has a clear getting-started section.
Setup 16/16 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, postbuild, dev, postinstall, lint, postlint…)
Makefile
–Environment config
n/a
Not applicable — this reads as a library, with no environment to configure.
✓Pinned runtime version
2/2
The language runtime version is pinned.
package.json engines.node ^24.0.0
✓Reproducible environment
2/2
.devcontainer/devcontainer.json gives a known-good environment.
Verification loop 25/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
1778 test files against 8840 source files.
e.g. .github/workflows/node-test.yml, apps/admin_audit/tests/Listener/SecurityEventListenerTest.php, apps/admin_audit/tests/Listener/UserManagementEventListenerTest.php
✓Test command is discoverable
7/7
An agent can find and run `npm run test`.
✓Continuous integration
4/4
59 GitHub Actions workflows define what "passing" means.
✓Lint and format rules
3/3
eslint.config.js encodes the house style.
✓Static type checking
3/3
Strict type checking is on, which catches a whole class of agent mistakes before they run.
Context economy 9/20 C
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 131 patterns.
✗File sizes fit in context
0/6
77 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/core-common.js — 5547KB
dist/emoji-C8k9NUlo-CPnPL868.chunk.mjs — 872KB
dist/workflowengine-workflowengine.js — 828KB
✗Repository weight
0/5
About 6984MB 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 ☁️ Nextcloud server, a safe home for all your data ## 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 postbuild npm run postinstall npm run postlint npm run lint:fix ``` ## Layout - `apps/` 4942 source files - `lib/` 2230 source files - `tests/` 840 source files - `core/` 469 source files - `dist/` 206 source files - `build/` 124 source files ## Conventions - Tests live alongside the code they cover, following `.github/workflows/node-test.yml`. - TypeScript runs in strict mode. Type errors are the fastest feedback available, so do not weaken it. - CI defines what passing means. See `.github/workflows/ai-policy.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/core-common.js` is 5547KB. 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/nextcloud/server.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/nextcloud/server)Other PHP 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.