datalicense

All datasets / mvd001

mvd001/cyberset

922 downloads in 30 days0 likesLast modified 4 Oct 2026View on Hugging Face
Possible licence conflict

The custom licence described in the dataset card and the licence detected in a repository file (cc-by-4.0) fall into different categories, so the licences may conflict.

Declared licence
other, from the tagEvidence: README.md at e623138
Licence name on the card
cyberset-mixed, link: LICENSE.mdEvidence: README.md at e623138
Licence files
LICENSE.md, detected as cc-by-4.0Evidence: LICENSE.md at e623138
Declared sources
None listed in the card metadata
Access gated on Hugging Face
No
mvd001/cybersetmvd001/cybersetcustom licence: declared licencecustom licencedeclared licenceREADME.md ↗cc-by-4.0: licence filecc-by-4.0licence fileLICENSE.md ↗
mvd001/cybersetmvd001/cybersetcustom licence: declared licencecustom licencedeclared licenceREADME.md ↗cc-by-4.0: licence filecc-by-4.0licence fileLICENSE.md ↗
Red marks the licence the signal is based on. Each cell links to what was checked: a file, a file list or a Hub record.

Tasks

Citation text from the card

@misc{mvd001_2026cyberset,
  author       = {{mvd001}},
  title        = {cyberset: a unified security ML dataset (knowledge hub, vulnerable/patched code, code graphs, network flows)},
  year         = {2026},
  howpublished = {Hugging Face dataset \url{https://huggingface.co/datasets/mvd001/cyberset}}
}

All datasets marked Possible licence conflict | JSON

The same facts for your agent

A free MCP server at mcp.datalicense.uk/mcp. Connect it from an MCP client such as Claude or Cursor.

dataset_licence({ "id": "mvd001/cyberset" })
signal: "conflict"
stated_licence: "other"
sources: 0