Parse and compile gettext po and mo files to/from json, nothing more, nothing less
84%
Total Score
63
100
89
80
50
No build attestation or trusted-publisher provenance is provided, leaving publication origin less independently verifiable; the established repository and release history provide some compensating transparency.
The repository is owned by an individual rather than an organization, so the concentrated recent commit activity is not offset by visible organizational handoff capacity.
Two contributors were active, but one made 11 of 12 recent commits. This creates meaningful maintainer-concentration risk for a user-owned project.
There are only eight open issues and two open pull requests, but no issues or pull requests were opened or closed in the last month. This is a mild activity gap, partially offset by recent commits and releases.
The repository reports no build tooling and no security scanning. The small, directly published JavaScript package makes the build gap less concerning, but the lack of scanning reduces supply-chain hygiene.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-10404 Pre-CVE Found by Aikido Intel before public disclosure or CVE publication. gettext-parser is vulnerable to Prototype Pollution in versions 0.1.0 - 9.0.1. | 0.1.0 - 9.0.1 | Medium |
| Dependency | Last Release | Score |
|---|---|---|
encoding Version ^0.1.13 | — | — |
content-type Version ^1.0.5 | — | — |
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.