# SLSA Provenance Policy Auditor (`q_services/slsa-provenance-auditor`) Actor

Audit in-toto SLSA provenance for subject digests, builder and build type allowlists, source expectations, timestamps and DSSE envelope presence.

- **URL**: https://apify.com/q\_services/slsa-provenance-auditor.md
- **Developed by:** [Q Services](https://apify.com/q_services) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.00 / 1,000 slsa provenance audits

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## SLSA Provenance Policy Auditor

Audit in-toto SLSA provenance statements and DSSE envelopes against explicit
artifact, builder, build-type and source expectations. The Actor validates
structure and policy locally and never downloads artifacts or dependencies.

### Important boundary

The Actor reports whether a DSSE signature is present but does not verify its
cryptographic trust chain. `cryptographicSignatureVerified` is always `false`.
Use a signer-specific verifier alongside this structural policy gate.

### Input

Each item in `provenances` can include `content`, `expectedSubjects`,
`allowedBuilderIds`, `allowedBuildTypes`, `allowedSourcePrefixes`,
`requireEnvelope` and `requireSignature`.

### Pricing

Pay per event: one `actor-start` event per run and one `dataset-item` event per
completed provenance audit.

# Actor input Schema

## `provenances` (type: `array`):

Each item contains name, content and optional expectations.

## `maxResults` (type: `integer`):

Maximum number of provenance documents processed in one run.

## Actor input object example

```json
{
  "provenances": [
    {
      "name": "artifact.intoto.jsonl",
      "content": {
        "_type": "https://in-toto.io/Statement/v1",
        "subject": [
          {
            "name": "app.tar.gz",
            "digest": {
              "sha256": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef"
            }
          }
        ],
        "predicateType": "https://slsa.dev/provenance/v1",
        "predicate": {
          "buildDefinition": {
            "buildType": "https://example.com/build/v1",
            "externalParameters": {},
            "resolvedDependencies": [
              {
                "uri": "git+https://github.com/acme/app@refs/heads/main",
                "digest": {
                  "gitCommit": "0123456789abcdef0123456789abcdef01234567"
                }
              }
            ]
          },
          "runDetails": {
            "builder": {
              "id": "https://example.com/builders/hosted"
            },
            "metadata": {
              "invocationId": "build-123",
              "startedOn": "2026-07-17T08:00:00Z",
              "finishedOn": "2026-07-17T08:02:00Z"
            }
          }
        }
      },
      "allowedBuilderIds": [
        "https://example.com/builders/hosted"
      ],
      "allowedBuildTypes": [
        "https://example.com/build/v1"
      ]
    }
  ],
  "maxResults": 200
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("q_services/slsa-provenance-auditor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("q_services/slsa-provenance-auditor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call q_services/slsa-provenance-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,q_services/slsa-provenance-auditor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/oTZafcye0yJMQbAcE/builds/lcpdETaSbh2x81Ged/openapi.json