OSSInsight widgets in this repository stop updating on December 4, 2026
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 82/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Open README.md and find the compose-last-28-days-stats image embed pointing at next.ossinsight.io; the announcement at https://ossinsight.io/blog/ossinsight-is-shutting-down explains why it stops refreshing after December 4, 2026. Decide with the maintainers between Repobeats, a static screenshot, or removing the widgets, then make the single edit. Done means the README no longer embeds the retiring OSSInsight widget and renders cleanly on GitHub.
Written by the indexing model from the issue text.
Description
Hi, I help maintain OSSInsight at PingCAP. OSSInsight is shutting down on December 4, 2026, and this repository embeds OSSInsight widget images from next.ossinsight.io.
README.md:compose-last-28-days-stats
What happens: the images won't break. After December 4 each one keeps showing its last snapshot with a small "no longer updates" note, so numbers such as "last 28 days" will be frozen.
If you'd like live charts, you could switch before then:
- Repository activity: Repobeats
Otherwise a static screenshot, or simply removing them, works too.
Announcement: https://ossinsight.io/blog/ossinsight-is-shutting-down
Thanks for featuring OSSInsight!
- Dominant language
- TypeScript
- Stars
- 39.3k
- Forks
- 2.2k
- Avg merge
- 9h 14m
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 RSSNext/Folo
-
bug platform: desktop
Difficulty 4/5 3-5 days Newbie friendliness 48/100
RSSNext/Folo#5139 · 1 comment ·
Maintainers usually reply within 1 day
-
bug need info platform: desktop
Difficulty 4/5 3-5 days Newbie friendliness 35/100
RSSNext/Folo#5055 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 50/100
RSSNext/Folo#5054 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
RSSNext/Folo#5053 · 1 comment ·
Maintainers usually reply within 1 day
-
Just show the titleOpenenhancement
Difficulty 3/5 1-2 days Newbie friendliness 58/100
RSSNext/Folo#5052 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Update project links after the repository renamesPossibly taken @JonathanTSilva claimed this today. Openai-generated priority: p2 size: xs type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
JonathanTSilva/jts-website#119 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
promplate/code-review#158 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
[Docs] CONTRIBUTING points the Backend Remake milestone at a branch that does not existPossibly taken @franpts2 claimed this today. Opendocs
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day