Validate a downloaded package in five checks: read the manifest, confirm each resource resolves, validate against the JSON Schemas, verify integrity with the published checksums, and confirm the version you pinned. Every check is an ordinary fetch of a static file — no API, no install.
- Manifest → resources → schema → checksums → version.
- Static files only; deterministic fingerprints.
- See also /developers/validation and /contract.
1 — Read the manifest
The package manifest lists every resource, schema, and the data-package version.
curl -s https://warconomy.com/datasets/conflict-economic-impact/package.json | jq '{version, manifestVersion, resourceCount}'2 — Confirm resources resolve
Each resource is a direct link; a HEAD/GET should return 200.
curl -s https://warconomy.com/datasets/conflict-economic-impact/package.json | jq -r '.resources[].path' | while read p; do echo "$p"; done3 — Validate against the schemas
Validate data.json against schema.json and each surface against its surface schema.
curl -s https://warconomy.com/datasets/conflict-economic-impact/schema.json -o schema.json
# validate https://warconomy.com/datasets/conflict-economic-impact/data.json against schema.json with any JSON Schema validator
# surface schemas: https://warconomy.com/datasets/conflict-economic-impact/schema-report4 — Verify integrity
Compare your copies against the published djb2 fingerprints and byte lengths.
curl -s https://warconomy.com/datasets/conflict-economic-impact/checksums.json | jq '.checksums[] | {path, fingerprint, bytes}'5 — Confirm the pinned version
If you pinned a version, confirm its frozen payload matches what you stored.
curl -s https://warconomy.com/datasets/conflict-economic-impact/versions/data.json | jq '.versions[0].version'More
Validation guide: /developers/validation · bundle: /datasets/conflict-economic-impact/bundle · checksums: checksums.json.