Is @inlang/language-tag safe to use?

@inlang/language-tag has no known vulnerabilities on the latest version (1.5.1). DepScope rates its health at 4/100 (critical risk).

What is the latest version of @inlang/language-tag?

The latest version of @inlang/language-tag is 1.5.1, released 2024-02-15.

Does @inlang/language-tag have known vulnerabilities?

No known vulnerabilities on the latest version of @inlang/language-tag.

Is @inlang/language-tag deprecated?

Yes, @inlang/language-tag is deprecated: use the inlang sdk directly https://www.npmjs.com/package/@inlang/sdk Consider using ? instead.

What are alternatives to @inlang/language-tag?

Popular alternatives to @inlang/language-tag in npm include: ?, semver, minimatch, debug, ansi-styles.

What license does @inlang/language-tag use?

@inlang/language-tag is licensed under Apache-2.0.

@inlang/language-tag

npmv1.5.1deprecated

[BCP-47 language tags](https://en.wikipedia.org/wiki/IETF_language_tag) types and validators.

License Apache-2.0permissive8 versions2 maintainers1 deps

/ 100

Health

find alternative

@inlang/language-tag is deprecated — find an alternative

Moderate health score (4/100) — verify manually
Package is deprecated

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

@sinclair/typebox

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@inlang/language-tag