datalicense

All datasets / vibrantlabsai

vibrantlabsai/pool-desk

1,340 downloads in 30 days0 likesLast modified 15 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 cd85aa2
Licence name on the card
per-task-mixed-permissive, link: https://huggingface.co/datasets/vibrantlabsai/pool-desk/blob/main/LICENSES.mdEvidence: README.md at cd85aa2
Licence files
LICENSES.md, detected as cc-by-4.0Evidence: LICENSES.md at cd85aa2
Declared sources
None listed in the card metadata
Access gated on Hugging Face
No
vibrantlabsai/pool-deskvibrantlabsai/pool-…custom licence: declared licencecustom licencedeclared licenceREADME.md ↗cc-by-4.0: licence filecc-by-4.0licence fileLICENSES.md ↗
vibrantlabsai/pool-deskvibrantlabsai/p…custom licence: declared licencecustom licencedeclared licenceREADME.md ↗cc-by-4.0: licence filecc-by-4.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" })
signal: "conflict"
stated_licence: "other"
sources: 0