docs: align README counts with the public registry
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 423
- Forks
- 53
- Avg merge
- 20h 26m
- Merged PRs (30d)
- 310
Description
The README and docs/FEATURES.md drifted from current source-backed counts after recent model and ABI additions.
Current drift:
- README reports 37 registered architectures;
scripts/check-supported-models.pyreports 40. - docs/FEATURES.md reports 38 registered architectures.
- README reports ABI v19 with 36 exports;
include/vllm.hdeclares ABI v20 with 45VLLM_APIexports. - README reports 36 tool-parser families and 40 names; the current public feature table and parser registry expose 38 families and 42 names.
- The News section does not mention the landed MiniMax-Music3 generation surface.
Acceptance: update the public docs from these source anchors and pass the README, public-doc-table, and supported-model checks without changing lifecycle or benchmark claims.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with README and docs/FEATURES.md, then verify the source anchors in scripts/check-supported-models.py and include/vllm.h. Update the documented architecture, ABI, tool-parser, and News counts without changing lifecycle or benchmark claims. Run the README, public-doc-table, and supported-model checks to confirm the documentation matches the registries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100