Is timezone_to_country safe to use?

timezone_to_country has no known vulnerabilities on the latest version (3.2.0). DepScope rates its health at 60/100 (moderate risk).

What is the latest version of timezone_to_country?

The latest version of timezone_to_country is 3.2.0, released 2026-02-25.

Does timezone_to_country have known vulnerabilities?

No known vulnerabilities on the latest version of timezone_to_country.

Is timezone_to_country deprecated?

No, timezone_to_country is actively maintained. Latest release: 3.2.0 (2026-02-25).

What are alternatives to timezone_to_country?

DepScope has no curated alternatives for timezone_to_country at this time.

What license does timezone_to_country use?

timezone_to_country is licensed under MIT.

timezone_to_country

pubv3.2.0

Extension method for translation Time Zone Id to ISO 3166-1 alpha-2 code (e.g. 'Asia/Seoul' to 'KR')

License MITpermissive13 versions3 deps4,939 weekly dl

/ 100

Health

safe to use

[email protected] is safe to use (health: 60/100)

Health breakdown0 – 100

20/25

maintenance

6/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (3)

flutter timezone flutter_timezone

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pub/timezone_to_country

Last updated · 2026-02-25T02:32:15.750727Z