Spaces:
Running
Running
Update README.md
Browse files
README.md
CHANGED
|
@@ -5,6 +5,135 @@ colorFrom: red
|
|
| 5 |
colorTo: yellow
|
| 6 |
sdk: static
|
| 7 |
pinned: false
|
|
|
|
|
|
|
| 8 |
---
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 9 |
|
| 10 |
-
Edit this `README.md` markdown file to author your organization card.
|
|
|
|
| 5 |
colorTo: yellow
|
| 6 |
sdk: static
|
| 7 |
pinned: false
|
| 8 |
+
license: mit
|
| 9 |
+
short_description: 'Security admission and adversarial test corpus for local AI '
|
| 10 |
---
|
| 11 |
+
LayerFault
|
| 12 |
+
|
| 13 |
+
Security admission for local AI models.
|
| 14 |
+
|
| 15 |
+
LayerFault is an offline-first security scanner and admission layer for AI models, model packages, repositories and runtimes.
|
| 16 |
+
|
| 17 |
+
This Hugging Face organisation hosts the LayerFault Security Corpus, a growing adversarial test corpus for validating AI model security scanners, admission controls and model-handling pipelines.
|
| 18 |
+
|
| 19 |
+
These repositories are security test fixtures, not models intended for inference.
|
| 20 |
+
|
| 21 |
+
|
| 22 |
+
## LayerFault Security Corpus
|
| 23 |
+
|
| 24 |
+
The corpus contains deliberately synthetic, malformed and adversarial model repositories designed to reproduce security conditions that defensive tooling should detect.
|
| 25 |
+
|
| 26 |
+
Coverage includes:
|
| 27 |
+
|
| 28 |
+
- unsafe Pickle and serialization
|
| 29 |
+
- NumPy object arrays
|
| 30 |
+
- Safetensors structural anomalies
|
| 31 |
+
- PyTorch and TorchScript packages
|
| 32 |
+
- Hugging Face custom loaders and `auto_map`
|
| 33 |
+
- tokenizer and template attacks
|
| 34 |
+
- hidden and Unicode instructions
|
| 35 |
+
- Python, PowerShell, JavaScript and shell capability chains
|
| 36 |
+
- executable and native library payloads
|
| 37 |
+
- archive and path traversal attacks
|
| 38 |
+
- suspicious sidecars
|
| 39 |
+
- dependency and package integrity anomalies
|
| 40 |
+
- malformed model formats
|
| 41 |
+
- provenance and lineage mismatches
|
| 42 |
+
- synthetic weight anomalies and backdoor fixtures
|
| 43 |
+
- dataset poisoning
|
| 44 |
+
- runtime security test cases
|
| 45 |
+
|
| 46 |
+
The corpus is organised into Hugging Face Collections so individual security domains can be explored and tested independently.
|
| 47 |
+
|
| 48 |
+
---
|
| 49 |
+
|
| 50 |
+
## Why LayerFault exists
|
| 51 |
+
|
| 52 |
+
A modern model repository can contain much more than weights.
|
| 53 |
+
|
| 54 |
+
```text
|
| 55 |
+
Model Repository
|
| 56 |
+
βββ weights
|
| 57 |
+
βββ configuration
|
| 58 |
+
βββ tokenizer
|
| 59 |
+
βββ templates
|
| 60 |
+
βββ Python code
|
| 61 |
+
βββ native libraries
|
| 62 |
+
βββ serialized objects
|
| 63 |
+
βββ scripts
|
| 64 |
+
βββ dependency metadata
|
| 65 |
+
```
|
| 66 |
+
|
| 67 |
+
These components can introduce conventional software security risks before a single inference request is made.
|
| 68 |
+
|
| 69 |
+
LayerFault places an admission boundary between acquiring a model and allowing it into an environment.
|
| 70 |
+
|
| 71 |
+
```text
|
| 72 |
+
MODEL ACQUISITION
|
| 73 |
+
β
|
| 74 |
+
βΌ
|
| 75 |
+
LAYERFAULT
|
| 76 |
+
β
|
| 77 |
+
βββ structure
|
| 78 |
+
βββ serialization
|
| 79 |
+
βββ package contents
|
| 80 |
+
βββ integrity
|
| 81 |
+
βββ provenance
|
| 82 |
+
βββ policy
|
| 83 |
+
βββ runtime exposure
|
| 84 |
+
β
|
| 85 |
+
βΌ
|
| 86 |
+
PASS / WARN / BLOCK
|
| 87 |
+
β
|
| 88 |
+
βΌ
|
| 89 |
+
INFERENCE
|
| 90 |
+
```
|
| 91 |
+
|
| 92 |
+
---
|
| 93 |
+
|
| 94 |
+
## Security Notice
|
| 95 |
+
|
| 96 |
+
Repositories published by this organisation may be intentionally adversarial.
|
| 97 |
+
|
| 98 |
+
Fixtures can contain synthetic examples of executable code, unsafe serialization constructs, malformed metadata, suspicious archive structures, malicious looking scripts or other behaviours that security tooling is expected to detect.
|
| 99 |
+
|
| 100 |
+
They are intended for:
|
| 101 |
+
|
| 102 |
+
- defensive security research
|
| 103 |
+
- scanner validation
|
| 104 |
+
- regression testing
|
| 105 |
+
- detector development
|
| 106 |
+
- model admission research
|
| 107 |
+
|
| 108 |
+
Do not treat corpus repositories as production models.
|
| 109 |
+
|
| 110 |
+
Do not execute arbitrary fixture contents outside an appropriately isolated testing environment.
|
| 111 |
+
|
| 112 |
+
---
|
| 113 |
+
|
| 114 |
+
## Security Boundaries
|
| 115 |
+
|
| 116 |
+
LayerFault can establish security properties about model artifacts, packages, provenance, runtimes and admission policy.
|
| 117 |
+
|
| 118 |
+
Static inspection cannot prove that arbitrary learned weights are free from semantic backdoors, hidden triggers or malicious learned behaviour.
|
| 119 |
+
|
| 120 |
+
LayerFault therefore keeps artifact security, runtime security and behavioural analysis as distinct guarantees.
|
| 121 |
+
|
| 122 |
+
---
|
| 123 |
+
|
| 124 |
+
## Corpus Purpose
|
| 125 |
+
|
| 126 |
+
The LayerFault Security Corpus exists to make model security testing:
|
| 127 |
+
|
| 128 |
+
- reproducible
|
| 129 |
+
- comparable
|
| 130 |
+
- regression friendly
|
| 131 |
+
- transparent
|
| 132 |
+
- easier to automate
|
| 133 |
+
|
| 134 |
+
The corpus is designed to evolve alongside new model formats, packaging methods, runtime behaviours and attack techniques.
|
| 135 |
+
|
| 136 |
+
---
|
| 137 |
+
|
| 138 |
+
**Know what you are admitting. Know whether it changed. Know who attested to it. Block execution when those guarantees fail.**
|
| 139 |
|
|
|