Is @lokalise/non-translatable-markup safe to use?

@lokalise/non-translatable-markup has no known vulnerabilities on the latest version (3.1.0). DepScope rates its health at 55/100 (high risk).

What is the latest version of @lokalise/non-translatable-markup?

The latest version of @lokalise/non-translatable-markup is 3.1.0, released 2025-06-19.

Does @lokalise/non-translatable-markup have known vulnerabilities?

No known vulnerabilities on the latest version of @lokalise/non-translatable-markup.

Is @lokalise/non-translatable-markup deprecated?

No, @lokalise/non-translatable-markup is actively maintained. Latest release: 3.1.0 (2025-06-19).

What are alternatives to @lokalise/non-translatable-markup?

Popular alternatives to @lokalise/non-translatable-markup in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @lokalise/non-translatable-markup use?

@lokalise/non-translatable-markup is licensed under Apache-2.0.

@lokalise/non-translatable-markup

npmv3.1.0

This package provides utils to work with non-translatable markup.

License Apache-2.0permissive15 versions16 maintainers0 deps1,658 weekly dl

lokalise/shared-ts-libs

/ 100

Health

use with caution

@lokalise/[email protected] low health (55/100) — consider alternatives

Moderate health score (55/100) — verify manually

Health breakdown0 – 100

10/25

maintenance

6/20

popularity

25/25

security

9/15

maturity

5/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

1.3 KBminified

0.7 KB gzipped

0 direct dependencies

side effectsscoped

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@lokalise/non-translatable-markup