CoolFace
Datasetpublic

LayerFault/dataset-clean-balanced-control

dataset-clean-balanced-control SECURITY TEST ARTIFACT: DO NOT USE AS A PRODUCTION MODEL This repository is part of the Layerfault synthetic security corpus. It is deliberately constructed to contain security-relevant characteristics for scanner testing. Corpus ID: LF-CH-DATA-0001 Purpose Dataset clean balanced control. Direct expected Layerfault rules None; this repository is a control/comparison input. Candidate rules These are… See the full description on the dataset page: https://huggingface.co/datasets/LayerFault/dataset-clean-balanced-control.

sourceHugging Faceapache-2.0updated 1mo agoView on Hugging Face
0likes17downloads
Dataset Card

dataset-clean-balanced-control

SECURITY TEST ARTIFACT: DO NOT USE AS A PRODUCTION MODEL

This repository is part of the Layerfault synthetic security corpus. It is deliberately constructed to contain security-relevant characteristics for scanner testing.

Corpus ID: LF-CH-DATA-0001

Purpose

Dataset clean balanced control.

Direct expected Layerfault rules

  • None; this repository is a control/comparison input.

Candidate rules

These are deliberately plausible targets that remain marked as candidates until the exact Layerfault build used for certification confirms them.

  • None

Negative-control rules

These should remain silent for this corpus item.

  • LF-DATASET-RARE-TRIGGER-CORRELATION
  • LF-DATASET-ZERO-WIDTH

Safety

The corpus uses fake secrets, loopback/.invalid network destinations, harmless marker output, and synthetic model behavior only. It is intended for static scanning and isolated security testing.

Challenge classification

  • Severity: informational
  • Difficulty: basic
  • Expected admission decision: PASS
  • Control type: negative
  • Attack surface: dataset-poisoning
  • Techniques: dataset, control
  • Transformations: none

Ground-truth oracle IDs

  • LF-ORACLE-DATA-0001

These oracle IDs describe synthetic ground truth. They do not claim that a matching Layerfault detector already exists. A challenge may intentionally expose a scanner blind spot and remain unmapped until the detector is implemented.