Increased readme badges

[thompson-tomo]

Add the npm version badge as well as the most recent npm release to give more info.

[PeterDaveHello]

Is there any reason to use a third-party badge instead of the official one when the existing one works well? I mean the CI badge: https://github.com/thlorenz/doctoc/actions/workflows/node.js.yml/badge.svg

[thompson-tomo]

Because it was a different color/style to the other 2 so changing it made it uniformed.

[PeterDaveHello]

Since the badges are visually distinct, reducing third-party dependencies will be better.

[thompson-tomo]

But it doesn't decrease third party dependencies as it is the same dependency as the other 2 badges.

Once a new release occurs, the 3rd badge will switch to green from the Red. With this change that green would be the same green otherwise it would be a different green, in fact it would even have a gradient.

[PeterDaveHello]

Thanks for the follow-up. I see where you're coming from regarding visual style.

However, since badge colors are dynamic and change based on status (passing vs. failing), perfect uniformity isn't really a permanent state we can rely on. I prefer to prioritize the reliability of the official source over matching the exact shade of green.

Would you be willing to revert the CI badge? I'd be happy to merge the rest of your contributions.

[Copilot]

Pull request overview

Adds additional README badges to surface npm package metadata alongside the existing CI status badge.

Changes:

• Switch the GitHub Actions badge to a shields.io-based badge.
• Add npm version and “last update” badges to the README header.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.