# pyradiomics 3.1.1.dev111+g8ed579383, is it safe?

**URL:** <https://discourse.slicer.org/t/pyradiomics-3-1-1-dev111-g8ed579383-is-it-safe/47416>\
**Category:** Radiomics\
**Tags:** python\
**Created:** [June 21, 2026, 11:18pm UTC](https://discourse.slicer.org/t/pyradiomics-3-1-1-dev111-g8ed579383-is-it-safe/47416 "2026-06-21T23:18:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![aujinen](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/aujinen/32/82516_2.png) [@aujinen](https://discourse.slicer.org/u/aujinen)\
**Post date:** [June 21, 2026, 11:18pm UTC](https://discourse.slicer.org/t/pyradiomics-3-1-1-dev111-g8ed579383-is-it-safe/47416/1 "2026-06-21T23:18:56Z")

</div>

I downloaded PyRadiomics using `git clone https://github.com/AIM-Harvard/pyradiomics` and installed it using `uv sync` according to the contents of “pyproject.toml” with C++ build tools of Microsoft “Build Tools for Visual Studio 2026”.  
The displayed PyRadiomics version is  
“pyradiomics 3.1.1.dev111+g8ed579383”  
Is this safe?  
It seems to be working correctly, but there’s no official information on versions above 3.1.0, which is confusing.  
With the advancement of AI, malware protection is essential for “uv” and libraries in “PyPI”, so I had set the environment variable “UV\_MALWARE\_CHECK” to “1” before running uv sync.  
Details in following URL (Sorry Japanese)

> **[uv で PyRadiomics を簡便にインストールする - Qiita](https://qiita.com/aujinen/items/035674c54ce138aa7a80)**
>
> Windows11・PowerShellでの手順 【注意】 今回、デフォルトのpythonが3.12の状態でインストールされていたため、自動的に3.12が設定されました。pyproject.toml内には requires-python ="\>=3.9" と記述されてお...

---

<div class="post-metadata">

**Author:** ![aujinen](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/aujinen/32/82516_2.png) [@aujinen](https://discourse.slicer.org/u/aujinen)\
**Post date:** [June 22, 2026, 8:07am UTC](https://discourse.slicer.org/t/pyradiomics-3-1-1-dev111-g8ed579383-is-it-safe/47416/2 "2026-06-22T08:07:01Z")

</div>

I found “pyradiomics 3.1.1.dev111+g8ed579383” by google search at following URL.

> <https://github.com/AIM-Harvard/pyradiomics/issues/929>
>
> Hello,
> 
> I have tried installing the Pyradiomics package using pip, conda, and fr…om source, and none of the options work for installing. I have tried installing on different python versions and with all previous pyraiodimics package versions and nothing has built correctly. Is anyone else having difficulties with installing? Has anyone else been able to recently install correctly? Thanks in advance for the help.

I’m not sure why the original site didn’t have a clear explanation of version 3.1.1 and how to “uv sync,” but it seems that the official information hasn’t been updated despite the content being changed to 3.1.1, resulting in an incomplete discrepancy. Alternatively, there might be a serious bug lurking in version 3.1.1 itself.

Does anyone have any more detailed information?

Personally, I’m happy that the functionality I need has been confirmed, but I think that if things continue like this, everyone won’t be able to use 3.1.1 with peace of mind.

---

<div class="post-metadata">

**Author:** ![aujinen](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/aujinen/32/82516_2.png) [@aujinen](https://discourse.slicer.org/u/aujinen)\
**Post date:** [June 25, 2026, 2:56am UTC](https://discourse.slicer.org/t/pyradiomics-3-1-1-dev111-g8ed579383-is-it-safe/47416/3 "2026-06-25T02:56:17Z")

</div>

The reason I wanted to install a standalone version of PyRadiomics—separate from 3D Slicer—is to create educational content that allows students to experience the actual process of radiomics image analysis calculations step-by-step.

Preliminary testing using Excel has already been conducted (see below).

> **[GitHub - aujinen/Microsoft-Excel-sheets-with-Macro-VB: Japanese](https://github.com/aujinen/Microsoft-Excel-sheets-with-Macro-VB)**
>
> Japanese

[Convolution-Radiomics-Wavelet.xlsx](https://github.com/aujinen/Microsoft-Excel-sheets-with-Macro-VB/blob/master/Convolution-Radiomics-Wavelet.xlsx "Convolution-Radiomics-Wavelet.xlsx")

I have forked the original PyRadiomics repository and named it “PyRadiomics\_edu.” Aside from the added `workspace` folder and a minimal README file, I have left the original content entirely unchanged and plan to add the educational materials within the `workspace` folder.

> **[GitHub - aujinen/pyradiomics\_edu: Educational version forked from Open-source python...](https://github.com/aujinen/pyradiomics_edu)**
>
> Educational version forked from Open-source python package for the extraction of Radiomics features from 2D and 3D images and binary masks. Support: https://discourse.slicer.org/c/community/radiomics

When I downloaded the aforementioned forked “PyRadiomics\_edu” repository using `git clone` and installed it following the same procedure with `uv sync`, the version became:  
`pyradiomics 0.1.dev1340+g15a938dad`  
**(is not 3.1.0 , 3.1.1)**  
If anyone knows the reason for this, I would appreciate your guidance.  
Additionally, please let me know if this practice is inappropriate, and I will delete the forked repository.

---

<div class="post-metadata">

**Author:** ![aujinen](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/aujinen/32/82516_2.png) [@aujinen](https://discourse.slicer.org/u/aujinen)\
**Post date:** [June 26, 2026, 1:50pm UTC](https://discourse.slicer.org/t/pyradiomics-3-1-1-dev111-g8ed579383-is-it-safe/47416/4 "2026-06-26T13:50:26Z")

</div>

Found it!  
It turned out to be the result of dynamic version management in `uv`, following the specifications in `pyproject.toml`.

“How to add dynamic versioning to uv projects”

> **[How to add dynamic versioning to uv projects](https://pydevtools.com/handbook/how-to/how-to-add-dynamic-versioning-to-uv-projects/)**
>
> Set up Git-based automatic version numbering in uv projects using uv-dynamic-versioning.