datalicense

All datasets / vibrantlabsai

vibrantlabsai/pool-desk-v2

1,193 downloads in 30 days0 likesLast modified 16 Oct 2026View on Hugging Face
Possible licence conflict

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

Declared licence
other, from the tagEvidence: README.md at c7eedb0
Licence name on the card
per-task-mixed-permissive, link: https://huggingface.co/datasets/vibrantlabsai/pool-desk-v2/blob/main/LICENSES.mdEvidence: README.md at c7eedb0
Licence files
LICENSES.md, detected as cc0-1.0Evidence: LICENSES.md at c7eedb0
Declared sources
None listed in the card metadata
Access gated on Hugging Face
No
vibrantlabsai/pool-desk-v2vibrantlabsai/pool-…custom licence: declared licencecustom licencedeclared licenceREADME.md ↗cc0-1.0: licence filecc0-1.0licence fileLICENSES.md ↗
vibrantlabsai/pool-desk-v2vibrantlabsai/p…custom licence: declared licencecustom licencedeclared licenceREADME.md ↗cc0-1.0: licence filecc0-1.0licence fileLICENSES.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

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": "vibrantlabsai/pool-desk-v2" })
signal: "conflict"
stated_licence: "other"
sources: 0