<img src="https://image.civitai.com/xG1nkqKTMzGDvpLrqFT7WA/5c6d59a1-5914-4ab4-9165-2d6f6c38f1de/width=525/5c6d59a1-5914-4ab4-9165-2d6f6c38f1de.jpeg" /><h1 id="loras-can-be-a-pain!-lwbffjjua">LoRAS CAN BE A PAIN!</h1>safetriggers.py is a CLI Python Script for Linux (tested on Ubuntu Server 24.10) capable of extracting the TAGS, TRIGGER-WORDS and TRIGGER-PHRASES from LoRAs trained on tagged source images and presenting them on screen OR saved as a;<pre><code>&lt;LoRA name&gt;.safetriggers</code></pre>file alongside your LoRA for distribution to users for quick reference, as a small and simple JSON text file.NOTE. LoRAs (*.safetensors) are UNAFFECTED and only ever read.Triggers are SORTED with most important FIRST in the list, in order of the occurance of tags in the source images, as trained.This makes it easy to see what a LoRA is really trained on and can be surprising.Q. LoRA USER! WANT AN EASY WAY TO SEE WHAT THE TRIGGERS ARE FOR A LoRA NAMED "foo_bar.safetensors"?<pre><code>python3 safetriggers.py --lora foo_bar</code></pre>Q. LoRA CREATORS! WANT AN EASY WAY TO MAKE A FILE TO ACCOMPANY YOUR LoRA TELLING USERS WHAT TRIGGERS MAKE YOUR LoRA NAMED "foo_bar.safetensors" WORK?<pre><code>python3 safetriggers.py --mksafetriggers --lora foo_bar</code></pre>Q. LoRA CREATORS! WANT AN EASY WAY TO SEE WHAT TAGS YOUR LoRA IN "./loras/foo_bar.safetensors" HAS BEEN TRAINED FOR AND WHAT IT HAS FOUND SIGNIFICANT FROM YOUR SOURCE IMAGES?<pre><code>python3 safetriggers.py --mksafetriggers --lorapath ./loras --lora foo_bar</code></pre>...and it will create a "./loras/foo_bar.safetriggers" file containg that info to process, read, examine or distribute with the .safetensors file.<h3 id="version-2025mar11-onward-hddupfvg9">VERSION 2025Mar11 onward;</h3>With the new -allloras option there's no need to name individual LoRAs using -lora so if you need to examine and generate .safetriggers files for all LoRAs in a -lorapath and subpaths then;<pre><code>python3 safetriggers.py --mksafetriggers --allloras --lorapath ./loras/nsfw</code></pre><h3 id="version-2025mar13-onward-8rfbtject">VERSION 2025Mar13 onward;</h3>With the new -safetriggers option you can name an individual LoRAs .safetriggers file and display its contents on-screen, for example;<pre><code>python3 safetriggers.py --lorapath ./loras/nsfw --safetriggers PrettyWomen-f1-v8</code></pre>to display on-screen the SORTED tags and trigger-words and trigger-phrases it has been trained on.<h3 id="version-2025mar16-onward-g8fyjbz3p">VERSION 2025Mar16 onward;</h3>With the new option you can name an individual LoRAs .safetriggers file and display its contents on-screen, for example;<pre><code>python3 safetriggers.py -p ./loras/nsfw -s PrettyWomen-f1-v8</code></pre>to display on-screen the SORTED tags and trigger-words and trigger-phrases it has been trained on.These shorter CLI parameters are listed on-screen by typing;<pre><code>python3 safetriggers.py -h</code></pre>NOTE.SOME LoRAs CONTAIN NO TAGS ( and safetriggers can identifty these) SO THERE'S NOTHING TO READ, SO YOUR ONLY OPTION IS TO CONTACT THE CREATOR OF THE LoRA TO DISCOVER HOW THEY INTENDED YOU TO USE IT!<h3 id="safetriggers.py-h41rfjuw5">safetriggers.py</h3>Use this handy tool for quickly examining the TAGS and TRIGGER-WORDS and TRIGGER-PHRASES in the META_DATA in LoRAs.To read a "&lt;LoRA name&gt;.safetriggers" text file in your code using this snippet;<pre><code>import os
import json

with open('lora.safetriggers') as f: 
 data = f.read()

lora_triggers_dictionary = json.loads(data)

print(lora_triggers_dictionary)</code></pre>DISCLAIMER;CURRENT VERSION IS ABLE TO READ AND ANALYZE SOME COMMON LoRA FORMATS BUT NOT ALL.Check later versions.<h2 id="note...-p4mwt2g5y">NOTE...</h2>INITIAL VERSION, A PROOF OF CONCEPT, WAS WRITTEN WHEN I WAS GETTING OVER A MIGRAINE AND SOME CODE DECISIONS MAY HAVE BEEN MADE USING A MAGIC-8-BALL, FOR WHICH I NOW HAVE REGRETS! USE LATER BETTER VERSIONS.

SAFETRIGGERS; Python Tool for READING TAGS & TRIGGERS FROM LoRAs

FASTERBETTERDEEPERAdded -allloras for processing ALL LoRAs in a folder, and subfoldersBug Fixes, Exceptions Caught &amp; Typos

Files with SHA256: 42872405d7d8a7367c77d3afbf2787b49ca1c6ee5fa7db571f6c046639a03f04