Is autotuning-methodology safe to use?

autotuning-methodology has no known vulnerabilities on the latest version (1.1.0). DepScope rates its health at 41/100 (high risk).

What is the latest version of autotuning-methodology?

The latest version of autotuning-methodology is 1.1.0, released 2025-09-03.

Does autotuning-methodology have known vulnerabilities?

No known vulnerabilities on the latest version of autotuning-methodology.

Is autotuning-methodology deprecated?

No, autotuning-methodology is actively maintained. Latest release: 1.1.0 (2025-09-03).

What are alternatives to autotuning-methodology?

Popular alternatives to autotuning-methodology in PyPI include: boto3, packaging, certifi, urllib3, idna.

What license does autotuning-methodology use?

autotuning-methodology is licensed under MIT.

autotuning-methodology

pypiv1.1.0

Software package easing implementation of the guidelines of the 2024 paper 'A Methodology for Comparing Auto-Tuning Optimization Algorithms' (https://doi.org/10.1016/j.future.2024.05.021). The DOI of this software is https://doi.org/10.5281/zenodo.11243974.

License MITpermissive8 versions21 deps2 weekly dl

fjwillemsen/autotuning_methodology

/ 100

Health

safe to use

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

Health breakdown0 – 100

10/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (21)

numpy scipy scikit-learn matplotlib yappi progressbar2 jsonschema nonconformist kernel_tuner pylint black sphinx sphinx_rtd_theme sphinx-pyproject ruff pep440 pytest pytest-cov nox crepes tomli

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/autotuning-methodology