The BIDS Validator
The BIDS Validator is a web application, command-line utility, and Javascript/Typescript library for assessing compliance with the Brain Imaging Data Structure (BIDS) standard.
Getting Started
In most cases, the simplest way to use the validator is to browse to the BIDS Validator web page:
The web validator runs in-browser, and does not transfer data to any remote server.
In some contexts, such as when working on a remote server, it may be easier to use the command-line. The BIDS Validator can be run with the Deno runtime (see Deno - Installation for detailed installation instructions):
deno run -ERWN jsr:@bids/validator
Deno by default sandboxes applications like a web browser.
-E, -R, -W, and -N allow the validator to read environment variables,
read/write local files, and read network locations.
A pre-compiled binary is published to PyPI and may be installed with:
pip install bids-validator-deno
bids-validator-deno --help
Configuration file
The schema validator accepts a JSON configuration file that reclassifies issues as warnings, errors or ignored.
{
"ignore": [
{ "code": "JSON_KEY_RECOMMENDED", "location": "/T1w.json" }
],
"warning": [],
"error": [
{ "code": "NO_AUTHORS" }
]
}
The issues are partial matches of the issues that the validator accumulates.
Pass the --json flag to see the issues in detail.
Development tools
From the repository root, use ./local-run to run with all permissions enabled by default:
# Run from within the /bids-validator directory
cd bids-validator
# Run validator:
./local-run path/to/dataset
Schema validator test suite
# Run tests:
deno test --allow-env --allow-read --allow-write src/
This test suite includes running expected output from bids-examples and may throw some expected failures for bids-examples datasets where either the schema or validator are misaligned with the example dataset while under development.
Modifying and building a new schema
To modify the schema a clone of bids-standard/bids-specification will need to be made. README and schema itself live here https://github.com/bids-standard/bids-specification/tree/master/src/schema.
After changes to the schema have been made to a local copy the dereferenced single json file used by the validator will need to be built. The bidsschematools python package does this. It can be installed from pypi via pip or a local installation can be made. It lives in the specification repository here https://github.com/bids-standard/bids-specification/tree/master/tools/schemacode
The command to compile a dereferenced schema is bst -v export --schema src/schema --output src/schema.json (this assumes you are in the root of the bids-specification repo). Once compiled it can be passed to the validator via the -s flag, ./bids-validator-deno -s <path to schema> <path to dataset>
Documentation
The BIDS validator documentation is available on Read the Docs.
2 maintainers
Metadata
2 maintainers
Release files for bids-validator-deno 3.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bids_validator_deno-3.0.2.tar.gz | 142.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bids_validator_deno-3.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.5 MB
Release files / bids_validator_deno-3.0.2.tar.gz
| Download URL | bids_validator_deno-3.0.2.tar.gz |
|---|---|
| Size | 142.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a1580cfa6f3320eff3551cb5af10916f4962a9365e76d39b9155a75470c8a45b
|
|
BLAKE2b-256 checksum How to use checksums |
51a999478a37eac0b8a55f5608b193301adb5754bcba7b097a2404b7d411fb3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / bids_validator_deno-3.0.2-py3-none-any.whl
| Download URL | bids_validator_deno-3.0.2-py3-none-any.whl |
|---|---|
| Size | 4.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2607e11f18c7da5d788771e474a9cf0c95ed044cb6c3824e57faf45a02eeb5cd
|
|
BLAKE2b-256 checksum How to use checksums |
e22cf93f3600283d4440d4a413f46bd4a5a8dbda5b3a137f4adff7c0ead34cf8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency log
