Datasets:

lanbass
/

canari-ledger

Error code:   StreamingRowsError
Exception:    ValueError
Message:      Expected object or value
Traceback:    Traceback (most recent call last):
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 291, in _generate_tables
                  pa_table = paj.read_json(
                      io.BytesIO(batch), read_options=paj.ReadOptions(block_size=block_size)
                  )
                File "pyarrow/_json.pyx", line 364, in pyarrow._json.read_json
                File "pyarrow/error.pxi", line 155, in pyarrow.lib.pyarrow_internal_check_status
                File "pyarrow/error.pxi", line 92, in pyarrow.lib.check_status
                  raise convert_status(status)
              pyarrow.lib.ArrowInvalid: JSON parse error: Column() changed from object to string in row 0
              
              During handling of the above exception, another exception occurred:
              
              Traceback (most recent call last):
                File "/src/services/worker/src/worker/utils.py", line 149, in get_rows_or_raise
                  return get_rows(
                      dataset=dataset,
                  ...<4 lines>...
                      column_names=column_names,
                  )
                File "/src/libs/libcommon/src/libcommon/utils.py", line 272, in decorator
                  return func(*args, **kwargs)
                File "/src/services/worker/src/worker/utils.py", line 129, in get_rows
                  rows_plus_one = list(itertools.islice(safe_iter(ds, dataset=dataset), rows_max_number + 1))
                File "/src/services/worker/src/worker/utils.py", line 544, in safe_iter
                  yield from ds.decode(False) if ds.features else ds
                File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 3052, in __iter__
                  for key, example in ex_iterable:
                                      ^^^^^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2559, in __iter__
                  for key, pa_table in self._iter_arrow():
                                       ~~~~~~~~~~~~~~~~^^
                File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2584, in _iter_arrow
                  for key, pa_table in self.ex_iterable._iter_arrow():
                                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
                File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 558, in _iter_arrow
                  for key, pa_table in iterator:
                                       ^^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 440, in _iter_arrow
                  for key, pa_table in self.generate_tables_fn(**gen_kwags):
                                       ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 306, in _generate_tables
                  batch = json_encode_fields_in_json_lines(original_batch, json_field_paths)
                File "/usr/local/lib/python3.14/site-packages/datasets/utils/json.py", line 111, in json_encode_fields_in_json_lines
                  examples = [ujson_loads(line) for line in original_batch.splitlines()]
                              ~~~~~~~~~~~^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/utils/json.py", line 20, in ujson_loads
                  return pd.io.json.ujson_loads(*args, **kwargs)
                         ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
              ValueError: Expected object or value

Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.

Canari Verification Ledger

Signed, offline-verifiable verification conclusions for AI agent components (MCP servers, npm packages, PyPI packages, dsh plugins), produced by real scans of public registries.

This is not a benchmark and not a labelled ML dataset. It is an audit ledger: a time series of what a verification pipeline concluded about a specific artifact, cryptographically bound to that artifact, with every re-scan preserved instead of overwriting the previous row.

Why it exists

Agent components are installed from public registries with almost no provenance. postmark-mcp shipped 15 clean versions and then a poisoned commit; after takedown no host was notified. The gap is not "detect the malicious package" - many scanners do that - it is that conclusions do not persist, do not travel, and cannot be checked by the party about to install the thing.

Each record here answers: for this exact artifact digest, what did the verification conclude, when, under which scenario, and what came before?

Path	What
`attestations/`	one DSSE/Ed25519 bundle per scan of one component
`feeds/`	`feed-multi-.json` (canonical per-component view), `run-feed-.json` (per-run)
`drift/`	per-run drift reports: verdict flips, same-version silent changes, findings deltas
`attestation-v0.1.json`	JSON Schema (draft 2020-12) of the predicate
`public_key.json`, `public_key_20261108.json`	Ed25519 public keys (two generations)
`key_registry.json`	key lifecycle (valid_from / valid_until / revoked_at)
`MANIFEST.json`	sha256 of every file in this dataset

Scale of this snapshot: 3251 attestations over 883 components across four registries (npm, PyPI, MCP Registry, dsh.so), 880 supersession chains, 13 run feeds, 3272 files.

Record format

The DSSE payload is a standard in-toto Statement v1, so GUAC, cosign and slsa-verifier can read it without any Canari-specific code:

Field	Value
`_type`	`https://in-toto.io/Statement/v1`
`subject[0].name`	`<registry>:<name>@<version>`
`subject[0].digest.sha256`	artifact sha256 - present only when the bytes were actually fetched
`subject[0].digest.canari-component-id`	sha256 of the component reference, used for metadata-only records instead of fabricating an all-zero hash
`predicateType`	`https://agentcheck.dev/attestation/v0.1`
`predicate.verdict`	`pass` / `pass-with-findings` / `fail` / `unsupported` / `error`
`predicate.checks`	per-check verdict + evidence reference
`predicate.supersedes`	payload digest of the previous attestation for the same component
`predicate.generated_at`, `predicate.expires_at`	when it was produced, when it goes stale

unsupported is deliberately distinct from pass: absence of evidence is not evidence of safety, and the gate blocks on it.

Verify it yourself

pip install canari-mcp
canari-verify attestations/<any>.bundle.json --key public_key.json
canari-verify --chain attestations/     # whole supersession DAG

No network, no account, no service. Then verify the snapshot itself against MANIFEST.json (3272 sha256 entries).

Honest limits

Risk signal, not a safety guarantee. pass means our checks found nothing, not that the component is safe.
Sample, not census. Coverage is what the registries expose publicly; this is a sample of each ecosystem.
Signature proves origin, not correctness. A valid signature proves the ledger produced the record - not that the verdict is right.
Weekly cadence, and records go stale. Every attestation carries expires_at (7 days). MANIFEST.json.generated_at says when this snapshot was cut.
581 of the 883 components carry no digest.sha256 (521 dsh.so + 60 MCP Registry). Those sources publish identity but no downloadable artifact, so the record uses digest.canari-component-id (sha256 of the component reference) instead of fabricating an all-zero artifact hash. The other 302 components carry a real sha256 obtained by fetching the artifact bytes (202 npm + 100 PyPI). 302 + 581 = 883.

License

Data: CC-BY-4.0. Code (the scanner + verifier that produced it): Apache-2.0, at https://github.com/lanbass869-cell/canari

Downloads last month: -

Total file size:

16.8 MB