Python Kroes workflow implementation (ttc_nccrp)
==============================
The foundation is taken from https://github.com/g-patlewicz/ttc_exclusions but relying on alerts described in Benigni et al (2008) https://publications.jrc.ec.europa.eu/repository/bitstream/JRC43157/eur%20report%20benigni%20130208%20final.pdf
An updated workflow to facilitate assigning of substances through the Kroes et al workflow. Substances are assigned as inorganics, out of scope of TTC due to their TCDD like features, steroid moiety, high potency genotoxic carcinogens, presenting a genotoxicity alert and organophosphates/carbamates. A new optional offramp exists for PFAS substances.
Specific Updates:
17-May-2026
- Adjusted simple aldehyde to cover formaldehyde
- Added new vinyl halides from Bailey et al Regul. Toxicol. Pharmacol. 2005; 42 (2) 225-35
- Adjusted hydrazine and nitroso patterns
- Added additional patterns for a number of other alerts
- Re-figured the logic for inorganics to capture alerting fragments for organic fragments when using SaltRemover.SaltRemover()
19-May-2026
- Added offramp for PFAS
- Created validation set to evaluate initial performance and refine all alerts that were resulting in discrepancies
Installation
This package requires RDKit. Dependencies are captured in the pyproject.toml file.
uv add ttc_nccrp
Licensing
This implementation is licensed under MIT.
Citation
Please cite Patlewicz and Mihalchik (2026) Revisiting the Threshold of Toxicological Concern: a computational framework for structural classification, cross-scheme comparison and opportunities for refinement. Computational Toxicology under review
Acknowledgements
A handful of SMARTS patterns and ring detection logic were developed with assistance from Claude Haiku (Anthropic), with subsequent code review to verify correctness.
1 maintainer
Metadata
1 maintainer
Release files for ttc-nccrp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ttc_nccrp-0.1.1.tar.gz | 107.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ttc_nccrp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 125.2 kB
Release files / ttc_nccrp-0.1.1.tar.gz
| Download URL | ttc_nccrp-0.1.1.tar.gz |
|---|---|
| Size | 107.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c329c71d5a586c1a56bae4b3ecf8834b3299f974eedfedbea14b34afecb5a01a
|
|
BLAKE2b-256 checksum How to use checksums |
6c03dfc506e13304c96ac5c8b82598f28f660206f35b0b17af52271f68f80c8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.23 {"installer":{"name":"uv","version":"0.11.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Pop!_OS","version":"22.04","id":"jammy","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / ttc_nccrp-0.1.1-py3-none-any.whl
| Download URL | ttc_nccrp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 17.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2516b416c31bc330cc3e27cb2d8915f98fd579f04b08496303f37a81cb357659
|
|
BLAKE2b-256 checksum How to use checksums |
bff33b54c0d0f747293ce53434df962550b649a7f3e47551f46644d31a4b98b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.23 {"installer":{"name":"uv","version":"0.11.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Pop!_OS","version":"22.04","id":"jammy","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for ttc-nccrp 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
