LTX-2.3-uncensored-v1.4
Otheruncensored
from Lightricks/LTX-2.3
↓ 66.7K♥ 932 repos
XORTRON-CriminalComputing-EnablementEngine-v0.3
XORTRON-CriminalComputing-EnablementEngine-v0.3 is a Heretic-ablated variant of darkc0de/XORTRON-CriminalComputing-EnablementEngine-v0.3, published on Hugging Face by darkc0de. It is apache-2.0 licence. It is distributed across 7 repositories in Transformers, MLX, GGUF and GGUF (imatrix) formats, totalling 11.2K downloads.
Specification
- Model name
- XORTRON-CriminalComputing-EnablementEngine-v0.3
- Source repository
- darkc0de/XORTRON-CriminalComputing-EnablementEngine-v0.3
- Publisher
- darkc0de
- Parameters
- Not determinable from name
- Hardware class
- Unknown
- Licence
- apache-2.0
- Task
- Image text to text
- Context window
- Not documented
- Ablation scope
- Not stated by the publisher
- Formats available
- Transformers, MLX, GGUF, GGUF (imatrix)
- First indexed
- 16 Aug 2026
- Last updated
- 17 Aug 2026
Ablation technique
How XORTRON-CriminalComputing-EnablementEngine-v0.3 was modified, and what that implies.
Heretic
Automated directional ablation via the Heretic toolchain, which searches for the refusal direction and applies it with a KL-divergence budget so general capability is preserved.
Reported scope: Not stated by the publisher. Publishers frequently omit this, so verify behaviour empirically rather than assuming full coverage.
From the publisher’s model card
“This model is a part of The XORTRON Criminal Computing project; an ongoing research experiment and exercise in AI safety and alignment.”
Running it
Commands are templates — confirm the exact repository and quant file before use.
llama.cpp / GGUF
hf download mradermacher/XORTRON-CriminalComputing-EnablementEngine-v0.3-i1-GGUF --local-dir ./xortron-criminalcomputing-enablementengine-v0.3
llama-cli -m ./xortron-criminalcomputing-enablementengine-v0.3/<file>.gguf -p "..."Transformers
from transformers import AutoModelForCausalLM, AutoTokenizer
repo = "darkc0de/XORTRON-CriminalComputing-EnablementEngine-v0.3"
tok = AutoTokenizer.from_pretrained(repo)
model = AutoModelForCausalLM.from_pretrained(
repo, torch_dtype="auto", device_map="auto"
)vLLM
vllm serve darkc0de/XORTRON-CriminalComputing-EnablementEngine-v0.3 --trust-remote-codeDownloads and variants (6)
Every published repository of XORTRON-CriminalComputing-EnablementEngine-v0.3, including quantised re-releases by other authors.
| Repository | Format | Downloads |
|---|---|---|
| mradermacher/XORTRON-CriminalComputing-EnablementEngine-v0.3-i1-GGUF | GGUF (imatrix) | 8.7K |
| mradermacher/XORTRON-CriminalComputing-EnablementEngine-v0.3-GGUF | GGUF | 1.3K |
| darkc0de/XORTRON-CriminalComputing-EnablementEngine-v0.3-GGUF | GGUF | 935 |
| darkc0de/XORTRON-CriminalComputing-EnablementEngine-v0.3source | Transformers | 207 |
| McG-221/XORTRON-CriminalComputing-EnablementEngine-v0.3-mlx-8Bit | MLX | 75 |
| spinochenza/XORTRON-CriminalComputing-EnablementEngine-v0.3 | Transformers | 13 |
Security-team assessment
Derived from this model’s metadata and the publisher’s claims — not from benchmarks run by this site.
- XORTRON-CriminalComputing-EnablementEngine-v0.3 will attempt offensive-security prompts that a hosted commercial model declines, which is what makes it usable for red-team corpus generation and for measuring what an unaligned model of this class produces.
- The publisher does not state which layers were ablated, so assume nothing about refusal consistency — probe it directly.
- Declared licence is apache-2.0, but the terms that bind you are darkc0de/XORTRON-CriminalComputing-EnablementEngine-v0.3’s — a re-release cannot grant more than its parent.
Handling: run it isolated, put moderation in front of it if anyone outside your team can reach it, and verify the weights before loading — these are third-party artifacts. Full handling and licence guidance.
Metadata for XORTRON-CriminalComputing-EnablementEngine-v0.3 is collected from the public Hugging Face API and the publisher’s model card. This site does not host weights, is not affiliated with darkc0de, and does not independently verify publisher claims. See responsible use.