Is layered_config_tree safe to use?

layered_config_tree has no known vulnerabilities on the latest version (4.1.7). DepScope rates its health at 59/100 (high risk).

What is the latest version of layered_config_tree?

The latest version of layered_config_tree is 4.1.7, released 2026-05-11.

Does layered_config_tree have known vulnerabilities?

No known vulnerabilities on the latest version of layered_config_tree.

Is layered_config_tree deprecated?

No, layered_config_tree is actively maintained. Latest release: 4.1.7 (2026-05-11).

What are alternatives to layered_config_tree?

Popular alternatives to layered_config_tree in PyPI include: boto3, packaging, python-dateutil, python-dotenv, pyjwt.

What license does layered_config_tree use?

layered_config_tree is licensed under BSD-3-Clause.

layered_config_tree

pypiv4.1.7

Layered Config Tree is a configuration structure which supports cascading layers.

License BSD-3-Clausepermissive30 versions1 maintainers12 deps

ihmeuw/layered_config_tree

/ 100

Health

use with caution

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

Moderate health score (59/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (12)

vivarium_dependencies[pyyaml]vivarium_build_utils vivarium_dependencies[ipython,matplotlib,sphinx,sphinx-click];sphinxcontrib-video;vivarium_dependencies[interactive];vivarium_dependencies[pytest];vivarium_dependencies[ipython,matplotlib,sphinx,sphinx-click];sphinxcontrib-video;vivarium_dependencies[interactive];vivarium_dependencies[pytest];vivarium_dependencies[lint];types-setuptools;

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/layered_config_tree