RSS feeds use Atom-style <author> elements, which are invalid in RSS 2.0

Open Beginner friendly
#2,577 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@NopeCharon is already working on this.

Since Nov 11, 2026.

  • #2578 by @NopeCharon — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
node.js, typescript

Research direction

Start with src/utils/rss.ts and inspect getAuthorsCustomData(), which is shared by both feeds. Check how author data is serialized into XML and how the RSS root is built; the issue identifies Dublin Core creator elements as the expected format. Done means both feeds use valid RSS author elements, names are XML-escaped, and feed validators accept them.

Written by the indexing model from the issue text.

Description

Environment information

Version: main at a3cb8630 and the live site, https://expressjs.com

Platform: any feed reader or feed validator

Node.js version: not relevant, this is generated build output

Any other relevant information: both feeds are affected, since they share getAuthorsCustomData() in src/utils/rss.ts.

What steps will reproduce the bug?

  1. Open https://expressjs.com/feed.xml or https://expressjs.com/vulnerabilities.xml.
  2. Look at any <item>.

Each item lists its authors like this:

<author><name>Ulises Gascon</name><uri>https://github.com/UlisesGascon</uri></author>

That's the Atom author format. In RSS 2.0, <author> is a text element that must hold the author's email address, and <name>/<uri> aren't defined there. Feed validators reject it, and readers either skip the author or show nothing useful.

The names are also inserted into the XML without escaping, so an author name containing & or < would corrupt the item.

Expected: each author appears in a valid RSS element. The usual choice for author names in RSS is Dublin Core's <dc:creator>, one per author, with the dc namespace declared on <rss>.

Dominant language
MDX
Stars
5.4k
Forks
2.3k
Avg merge
2d 23h
Merged PRs (30d)
28

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from expressjs/expressjs.com

All issues in expressjs/expressjs.com

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.