Verify a static deployment matches its build manifest

Created by

Axel Hu

Actor

Release Integrity & Deployment Auditor

Verify that a public static deployment serves the expected decoded bytes, SHA-256, size, MIME type, redirects, CORS, and cache policy from a build manifest.

Try for free

Release Integrity & Deployment Auditoraxelhu/release-integrity-auditor

Overall

Receipt digest

Input digest

Rules digest

+4 fields

Input

Expected release manifest(required):{4 fields}

Output fields

Overall

Receipt digest

Input digest

Rules digest

Manifest

Totals

Findings

Objects

How it works

Sign up on Apify or log in

The Release Integrity & Deployment Auditor Actor is ready to run with the inputs already set for "Verify a static deployment matches its build manifest". Sign up or log in and you'll land in Apify Console with a copy of this exact task.

Start the "Verify a static deployment matches its build manifest" task

The Release Integrity & Deployment Auditor Actor will start running based on the input automatically. You can also change all the input fields, like expected release manifest, to match your specific use case.

Receive the "Verify a static deployment matches its build manifest" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as overall, receipt digest, input digest, and more.

Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Verify a static deployment matches its build manifest" task via API.