Parse `.git/config` into a JavaScript object. sync or async.
56%
Total Score
50
100
86
88
50
No build attestation or staged publishing was detected, leaving publication provenance less verifiable. This is a supply-chain transparency gap, not a health verdict by itself.
The package has 19 releases but none in the last 12 months; its latest release was in November 2018, over seven years ago. This is a substantial maintenance concern, although the stable 3.0.0 release and small scope partly offset it.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating little current maintenance capacity.
There were no new or closed issues or pull requests in the last month, while three issues and two pull requests remain open. This suggests limited recent project response.
The repository uses a build tool, but no security scanning tools were detected. For a small library this is a hygiene gap rather than evidence of abandonment on its own.
| Title | Versions | Severity |
|---|---|---|
CVE-2025-25975 parse-git-config is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor in versions 0.0.0 - 3.0.0. | 0.0.0 - 3.0.0 | High |
| Dependency | Last Release | Score |
|---|---|---|
ini Version ^1.3.5 | — | — |
git-config-path Version ^2.0.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.