Export schema
This page is the schema for the full data export: what the bundle contains and the shape of each record. How to start an export, verify it and what limits apply are on the data export page. The Data Processing Agreement §9 points here.
Bundle layout
export-<your-org-slug>-<YYYY-MM-DDTHH-MM-SS-mmmZ>.tar.gz
├── VERIFY.md — step-by-step verification recipe
├── manifest.json — every file below, SHA-256 and size
├── manifest.json.intoto.jsonl — DSSE-signed in-toto Statement over manifest.json
├── audit.ndjson — your org's audit events, last 90 days
├── access-log.ndjson — your registry access log (package and container downloads, uploads and deletes; CI cache hits are in pulled-versions.ndjson)
├── bundles/
│ ├── <repo>.bundle — git bundle: full history, every ref
│ └── <repo>.empty — instead of a bundle, for a repository with no commits (zero bytes)
├── findings/ — scan findings, see "Scan findings, policy, attestations and SBOMs" below
├── policy/ — package policy, verdicts, exceptions and scanner settings
├── attestations/ — build provenance and release attestations, with their signatures
├── sboms/ — repository and container-image SBOMs, with an index
└── metadata/
├── packages.ndjson — package inventory, see "Packages" below
├── packages-files.ndjson — every file of every package version
├── packages-container-tags.ndjson — container image tag → manifest digest
├── components.ndjson — third-party component inventory, see "Component inventory" below
├── deployments.ndjson — deployments your CI/CD reported, see "Deployments" below
├── pulled-versions.ndjson — package versions pulled per day and consumer, see "Pulled versions" below
└── <repo>/
├── repo.ndjson — repository settings, description, topics
├── issues.ndjson — every issue, open and closed
├── pulls.ndjson — every pull request, open and closed
├── comments.ndjson — issue and pull-request comments
├── labels.ndjson
├── milestones.ndjson — open and closed
├── releases.ndjson — release metadata; see "Release assets" below
└── lfs-manifest.ndjson — LFS object inventory, see "LFS content" belowRepository names containing characters outside a-z 0-9 . _ - appear with those characters replaced by _.
Standards used:
- Repos: Git’s native
git bundleformat.git clone <bundle>reconstructs the repo end-to-end, including history, branches and tags. A repository with no commits has nothing to bundle and appears as an empty<repo>.emptyfile instead. - Issues, pull requests and the other
metadata/files: NDJSON, one JSON object per line, in the same shape the Forgejo API returns for each object. - Audit log: NDJSON, one event per line (
id,action,actor,fields_json,created_at). Same shape as fremforge’s internal audit stream. - Registry access log: NDJSON, oldest first, one event per line in the shape
GET /orgs/{slug}/access-logreturns, with client IPs and logins as recorded. It covers everything still held under your audit log retention. See Registry access log. - Integrity:
manifest.jsonlists every file with its SHA-256 hash and size. The manifest is DSSE-signed with fremforge’s Ed25519 builder key, the signature lives inmanifest.json.intoto.jsonland verifies against the public trust root athttps://www.frem.sh/.well-known/slsa-trust-root.jsonusingopenssl,jq,python3, andcurl, no fremforge tooling required. The full recipe is inVERIFY.mdinside the bundle and in §“Verifying the signed manifest” on the data export page. This is the same trust root published for SLSA build attestations, one key, two predicate types, zero Sigstore dependency.
No proprietary formats. Every artifact in the bundle reads with standard OSS tooling. No fremforge CLI required.
Packages
metadata/packages.ndjson is the inventory of your org’s package registry: one line per package version, with its type (container, npm, maven, pypi, generic, …), name and version, as the Forgejo package API lists them.
metadata/packages-files.ndjson lists every file of every one of those versions, one line per file:
| Field | Meaning |
|---|---|
owner, type, name, version | the package version the file belongs to |
file_id, file_name | the file’s identifier and name in the registry |
size | size in bytes |
sha256 | SHA-256 of the file; sha512 as well where the registry records one |
download_path | path on frem.sh that downloads exactly this file with an API token (Authorization: token …); the registry may answer with a redirect to object storage. null for registry types whose file URL can’t be derived from the inventory alone (for example Maven); use web_path for those |
web_path | the file’s download link on its package page, for a signed-in browser |
For container images, a package version is a tag (or, for an untagged manifest such as one platform of a multi-arch image, the digest itself). metadata/packages-container-tags.ndjson maps each tag to its manifest digest (owner, name, tag, manifest_digest), which is what docker pull <image>@sha256:… and other OCI tools use. The image’s layers and config appear in packages-files.ndjson as files named by their digest, with download_path pointing at the registry’s /v2/…/blobs/… and /v2/…/manifests/… endpoints.
Check a downloaded file against the inventory:
row=$(jq -c 'select(.name=="@acme/lib" and .version=="1.2.0")' metadata/packages-files.ndjson)
curl -sSL -H "Authorization: token $TOKEN" -o pkg.bin "https://frem.sh$(jq -r .download_path <<<"$row")"
echo "$(jq -r .sha256 <<<"$row") pkg.bin" | sha256sum -c -The inventory is always in the bundle. The package files themselves come only on request, as a separate archive: see §“Package contents”.
Component inventory
metadata/components.ndjson is your org’s third-party component inventory: one line per component and place it is or was used, the same rows GET /orgs/{slug}/components/usages answers. Uses that have ended are kept for 180 days and are included, so the history leaves with you.
| Field | Meaning |
|---|---|
purl, ecosystem, name, version | the component, as a package URL and its parts |
licence, licence_source | the licence expression, and where it was read from |
subject_kind, subject_name, subject_ref | where it is used: the repository, package or image, and the ref or digest |
image_tags | for an image, the tags pointing at it; otherwise empty |
source_repo | the repository that built it, where known |
is_direct | true for a direct dependency, false for a transitive one, null where the SBOM does not say |
environment, environment_source | the environment class (sandbox, development, test or production) and how it was set |
is_current, first_seen_at, last_seen_at, removed_at | whether the use is current, and when it was first and last seen and removed |
Deployments
metadata/deployments.ndjson holds every deployment your CI/CD reported with POST /orgs/{slug}/repos/{repo}/deployments, one line per deployment, oldest first by identifier.
| Field | Meaning |
|---|---|
id | the deployment’s identifier |
repository, environment, environment_class | the repository (owner/name), the environment name you gave, and its class (sandbox, development, test, staging or production) |
ref, sha, task, description | the ref and commit deployed, the task (deploy unless you gave another) and your description |
image_digests, packages | the image digests and package URLs the deployment names |
state | the latest status: pending, queued, in_progress, success, failure, error or inactive |
creator_kind, creator, run_id | who reported it (job, robot, user or token), its name, and the Actions run for a job |
created_at, updated_at | when it was reported and last changed |
statuses | every status, newest first: state, description, log_url, environment_url, creator_kind, creator, created_at |
Pulled versions
metadata/pulled-versions.ndjson is the pull census: one line per UTC day, package version and consumer, for the days still held under your access log retention. Since 2026-10-13 it is the only record of the downloads a CI job made through the dependency proxy that were served from its cache; those are not in access-log.ndjson. These are the rows GET /orgs/{slug}/components/pulled adds up; the advisories that endpoint joins are not in the file.
| Field | Meaning |
|---|---|
day | the UTC day, YYYY-MM-DD |
origin | registry for your own packages, proxy for the dependency proxy |
ecosystem, name, version | the package type (npm, pypi, maven, nuget, go, container, …), name and version |
consumer | who pulled it: kind (job, robot, bot, user or anonymous), name (the job’s repository, the robot’s name or the login; null for anonymous), id, for a robot its login, and for a job run_ids, the Actions runs that pulled it that day (newest first, at most 100; empty before 2026-10-13) |
pulls | successful downloads that day |
first_seen_at, last_seen_at | the first and last of them, UTC with microseconds |
Scan findings, policy, attestations and SBOMs
Every export carries the security data fremforge holds about your org, as NDJSON (one JSON object per line), covered by the signed manifest like every other file. Each line is the full record fremforge stores, except the internal tenant id and storage paths; dismissed findings are included with who dismissed them, why, and until when. Rows that concern a registry package carry a package object (type, owner, name, version, file, blob_sha256).
findings/
├── sast.ndjson — static analysis (rule, file, line, severity)
├── dependencies.ndjson — dependency vulnerabilities, with CVSS and EPSS where known
├── dependency-dismissals.ndjson — repository-wide dependency dismissals
├── licences.ndjson — licence findings, each with its licence policy decision
├── container-images.ndjson — container image vulnerabilities
├── container-image-dismissals.ndjson
├── secrets.ndjson — rule, file, line and fingerprint; the secret value is never stored
├── secrets-public-leaks.ndjson — frem.sh credentials found in public code: public URL, repository, commit,
path, line, when found, token kind and reference, and what was done;
never the token or a hash of it
├── malware-uploads.ndjson — malware found in uploads
├── malware-dependencies.ndjson — known-malicious dependencies
├── malware-container-layers.ndjson — per image manifest, each layer's malware verdict
├── packages.ndjson — vulnerabilities found in your registry packages
├── package-licences.ndjson — declared and detected licences of your registry packages
└── sha-pinning.ndjson — workflow actions not pinned to a commit
policy/
├── package-policy.ndjson — your package policy (mode, thresholds, licence lists, minimum age)
├── package-policy-rules.ndjson — allow and deny rules
├── package-policy-approvers.ndjson
├── package-policy-verdicts.ndjson — the current verdict for each package file, with reasons
├── package-gate-decisions.ndjson — downloads blocked, or that would have been blocked in shadow mode
├── exceptions.ndjson — policy exceptions, who requested and who approved them
├── malware-overrides.ndjson
├── package-access-packages.ndjson — per-package access: each configured package (mode, inheritance)
├── package-access-grants.ndjson — per-package access grants (teams, Actions repositories)
├── package-protection-rules.ndjson — protected package names
├── scan-overrides.ndjson — per-repository scanner mode overrides
└── settings/ — each scanner's org settings (sast, dependencies, licences, container-images, secrets),
and licence-repo-overrides.ndjson: per-repository licence policy overrides
and package-access.ndjson: the per-package access default
and retention.ndjson: one line per evidence retention class, with what you set,
what applies, the default, the bounds and whether a legal hold is active
and public-leak.ndjson: public leak monitoring, notify and revoke or notify only
attestations/
├── build-provenance.ndjson — one line per build provenance attestation
├── build-provenance/<id>.intoto.jsonl — its DSSE envelope (the Ed25519 signature)
├── build-provenance/<id>.sigstore.json — its keyless Sigstore bundle, where one was made
├── releases.ndjson — release attestations: subjects, the frozen release manifest, status, and envelope_path
├── sbom-ingest.ndjson — attestations uploaded together with an SBOM
└── sbom-ingest/<sbom id>.intoto.jsonl
sboms/
├── index.ndjson — one line per SBOM, see below
├── repos/<id>.cdx.json — a repository SBOM, CycloneDX (<id>.spdx.json for SPDX)
└── images/<id>.cdx.json — a container image SBOM- Signatures travel with the attestations. Each envelope verifies against the same trust root as the bundle, with the script in §“Verifying the signed manifest” pointed at the envelope instead of
manifest.json.intoto.jsonl(skip themanifestSha256andpredicateTypechecks, which apply to export bundles only). The Sigstore bundles are signed against fremforge’s own Fulcio and timestamp authority, not public Sigstore; see SLSA provenance. - A missing signature is shown, not hidden. A line with
"envelope_status": "missing"is an attestation whose signature object was no longer in storage when the export ran. Any other storage error fails the export. - Container layers. A layer’s malware verdict belongs to its content, so a layer shared with another image is listed with its verdict under each of your manifests that uses it. Images pulled through the dependency proxy are listed only while your organisation has ClamAV scanning of proxied fetches turned on; with it off (the default) they are not ClamAV-scanned and have no layer verdicts.
- Release attestations exist for repositories with immutable releases. A release whose
statusis notsignedhas no envelope (envelope_pathisnull). - SBOMs.
sboms/holds every SBOM fremforge stores for your repositories (release and default-branch builds, whether uploaded or produced by the central scan) and for your container images (the registry’s per-manifest inventory), as the document itself. A repository build usually has both a CycloneDX and an SPDX document; see SBOMs. Each line ofsboms/index.ndjsonis the stored SBOM record (id,subject_kindrepoorimage,format,repo_full_nameorartifact_name,release_tag,image_tags,manifest_digest,created_at,sha256_digestand the rest of the stored record, without storage paths) plus three fields about the file in this bundle:document_path,document_sha256, anddocument_status, which isokwhen the document matches the SHA-256 recorded when it was stored,digest_mismatchwhen it does not (the bytes are exported anyway, and both digests are on the line), andmissingwhen the document was no longer in storage. Any other storage error fails the export. - Package SBOMs are not in
sboms/. Each registry package file’s SBOM travels next to the file in the opt-in package contents archive.