Offer: self-updating EOL badge for your supported-versions table

Open
#11,726 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
markdown
Domain
documentation

Research direction

Review the manually maintained supported-versions tables in README and SECURITY.md, then compare them with the proposed Shields.io endpoint badge snippet. Confirm where a badge would belong and whether the external endoflife.ai data is acceptable; done means the maintainers approve a specific documentation change or close the proposal.

Written by the indexing model from the issue text.

Description

Hi — I noticed you maintain LoopBack’s own long-term support table by hand in your README and SECURITY.md. We run endoflife.ai (lifecycle data for 488 products, built on the endoflife.date community dataset — we're contributors) and publish free Shields.io endpoint badges that show live support status:

LoopBack EOL

[![LoopBack EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Floopback.json)](https://endoflife.ai/loopback)

When a version reaches end of life, the badge updates itself — no README edits, no CI. There are per-version badges too (e.g. pin the minimum version you support, so the badge flips the day your floor goes EOL). No signup, no tracking, no API keys — they're static JSON endpoints in the Shields endpoint format, regenerated nightly from vendor lifecycle policies.

If it's useful, the copy-paste snippet for your stack is one click at endoflife.ai/badge; if not, feel free to close this — no hard feelings. Not affiliated with any of your dependencies; just trying to make EOL status visible where people actually look. (Background: why we built these.)

Dominant language
TypeScript
Stars
5.1k
Forks
1.1k
Avg merge
2d 20h
Merged PRs (30d)
34

Contributor guide

Open the contributing guide

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 loopbackio/loopback-next

All issues in loopbackio/loopback-next

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.