Badge request: Locked npm dependency version from package-lock.json
- Dominant language
- JavaScript
- Stars
- 27.2k
- Forks
- 5.6k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 46
Description
:clipboard: **Description**
[](https://img.shields.io/npm/v/mermaid?color=teal&label=mermaid&logo=npm)
Shows the exact version of a package found in `package-lock.json`.
:link: **Data**
Retrieving the data should function pretty much the same way as it already works for `package.json`.
:microphone: **Motivation**
This badge should co-exist with the already existing `package.json` badge. The only difference would be that it gets the module's version from `package-lock.json` which allows you to show on which exact version of a package your code currently depends on.
Contributor guide
Research direction
Start by locating the existing package.json badge implementation and its data-retrieval entry point, then compare how a dependency is represented in package-lock.json. Done means the badge can report the exact locked package version while co-existing with the package.json badge; check the existing badge tests or endpoint behavior for consistency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100