The Policy and the Packet Public App Transparency Lab
Release 1.0: platform and standard live; no real packet audits yet August 6, 2026
Open data · API v1

The same proposition in the interface and in JSON

The registry, calibration receipts, relationships and repairs can be downloaded directly. The API does not remove evidentiary limits from the data; state and calibration fields must be preserved.

01

Exports

registry.jsonJSONregistry.csvCSVreceipts.jsonJSONrepair-ledger.jsonJSONdependencies.jsonJSONrelease.jsonJSON
02

Endpoints

GET /politica-si-pachetul/api/v1/registryJSON
GET /politica-si-pachetul/api/v1/receiptsJSON
GET /politica-si-pachetul/api/v1/repairsJSON
GET /politica-si-pachetul/api/v1/dependenciesJSON
GET /politica-si-pachetul/api/v1/releaseJSON
curl -s https://mariuscomper.uk/politica-si-pachetul/api/v1/registry | jq '.apps | length'
03

Reuse rules

  • Preserve audit_level, catalogue_status and is_calibration in every derivative.
  • Do not turn registered_not_audited into a finding about an app.
  • Do not strip limitation or provenance fields from a public quotation.
  • Use the stable version URL and state the export date.

CORS and caching

API responses permit cross-origin reading and use short public caching with stale-while-revalidate. Static versioned assets are immutable.