Is gettext-to-messageformat safe to use?

gettext-to-messageformat has no known vulnerabilities on the latest version (0.4.0). DepScope rates its health at 49/100 (high risk).

What is the latest version of gettext-to-messageformat?

The latest version of gettext-to-messageformat is 0.4.0, released 2021-04-10.

Does gettext-to-messageformat have known vulnerabilities?

No known vulnerabilities on the latest version of gettext-to-messageformat.

Is gettext-to-messageformat deprecated?

No, gettext-to-messageformat is actively maintained. Latest release: 0.4.0 (2021-04-10).

What are alternatives to gettext-to-messageformat?

Popular alternatives to gettext-to-messageformat in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does gettext-to-messageformat use?

gettext-to-messageformat is licensed under MIT.

gettext-to-messageformat

npmv0.4.0

Convert gettext input (po/pot/mo files) into messageformat-compatible JSON

License MITpermissive6 versions1 maintainers1 deps31,845 weekly dl

eemeli/gettext-to-messageformat

/ 100

Health

use with caution

[email protected] low health (49/100) — consider alternatives

Moderate health score (49/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

gettext-parser

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/gettext-to-messageformat