RSS feeds use Atom-style <author> elements, which are invalid in RSS 2.0
Maintainers usually reply within 1 day
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
- Domain
- backend, documentation
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?
- Open https://expressjs.com/feed.xml or https://expressjs.com/vulnerabilities.xml.
- 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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from expressjs/expressjs.com
-
Sitemap lists hundreds of URLs that declare a different canonicalPossibly taken @NopeCharon claimed this 13 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
expressjs/expressjs.com#2568 ·
Maintainers usually reply within 1 day
-
llms.txt exports drop `import` lines and JSX-like code from code examplesPossibly taken @RaphaelFakhri claimed this 16 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
expressjs/expressjs.com#2561 ·
Maintainers usually reply within 1 day
-
Remove problematic examples from error handling guidePossibly taken @Skytuhua claimed this 24 days ago. Openbug require-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
expressjs/expressjs.com#2549 · 1 reaction ·
Maintainers usually reply within 1 day
-
Suggestion: mention lint-time security checks on the security best practices pagePossibly taken @methila-2056 claimed this 85 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
expressjs/expressjs.com#2471 ·
Maintainers usually reply within 1 day
-
Document customizing `express.json()` size limit for specific routesPossibly taken @vibhor-aggr claimed this 132 days ago. Open4.x 5.x docs
Difficulty 1/5 Under an hour Newbie friendliness 62/100
expressjs/expressjs.com#1421 · 3 comments · 2 reactions ·
Maintainers usually reply within 1 day
All issues in expressjs/expressjs.com
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
it-at-m/Wahllokalsystem#3846 ·
Maintainers usually reply within 2 days
-
DoRA magnitude vectors are not loaded by Transformers load_adapter / from_pretrained(adapter_dir)Openpost-v1
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
huggingface/peft#4208 · 1 comment ·
Maintainers usually reply within 1 day
-
Area/Connector module/solace Priority/Low Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
ballerina-platform/ballerina-library#9849 ·
Maintainers usually reply within 1 day
-
issue: bug report
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
cloudamqp/amqp-client.cr#98 ·
Maintainers usually reply within 1 day