Is callsign-regex safe to use?

callsign-regex has no known vulnerabilities on the latest version (0.7.1). DepScope rates its health at 38/100 (critical risk).

What is the latest version of callsign-regex?

The latest version of callsign-regex is 0.7.1, released 2024-12-20.

Does callsign-regex have known vulnerabilities?

No known vulnerabilities on the latest version of callsign-regex.

Is callsign-regex deprecated?

No, callsign-regex is actively maintained. Latest release: 0.7.1 (2024-12-20).

What are alternatives to callsign-regex?

Popular alternatives to callsign-regex in PyPI include: boto3, packaging, urllib3, idna, certifi.

What license does callsign-regex use?

callsign-regex is licensed under OSI Approved :: MIT License.

callsign-regex

pypiv0.7.1

Match ham radio callsigns based on ITU appendix42

License OSI Approved :: MIT License8 versions1 maintainers1 deps

mahtin/callsign-regex

/ 100

Health

use with caution

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

Moderate health score (38/100) — verify manually

Health breakdown0 – 100

5/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

openpyxl

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/callsign-regex