Trust centre · Verify everything you run
MAQPNA security and supply-chain verification.
Every release is signed, every image carries an SBOM, and nothing calls home.
Keyless signatures, bound to the workflow that built them
Binaries
Sigstore bundle per file, plus signed checksums.
11 images
Multi-arch, distroless, non-root, SBOM attested.
Helm chart
A signed OCI artifact.
SBOM and provenance
SPDX 2.3 and SLSA build provenance.
Verify a download
Checksum and signature, in one command.
maqpna verify checks binaries, images, the chart and air-gap bundles. Manual cosign commands are on the download page.
# one binary, against its Sigstore bundle and checksums.txt
maqpna verify binary maqpna_linux_amd64 --bundle maqpna_linux_amd64.sigstore.json --checksums checksums.txt
# a whole release: images, chart and SBOM attestations
maqpna verify release v2.2.0 --sbomSecure defaults
Safe until you say otherwise.
Default deny
No rule, no call. No egress by default.
Fail closed
No revocation list means no calls.
Hardened sandboxes
Non-root, read-only, no service-account token.
No phone-home
An unexpected outbound call is a vulnerability.
- govulncheck
- staticcheck
- Trivy on every image
- Nightly fuzzing
- kind e2e with gVisor
OWASP Top 10 for Agentic Applications (2026)
Every risk, mapped to a control.
"Mitigates" means the root cause lies elsewhere, usually in the model. The full control-by-control explanation is in the OWASP Top 10 for Agentic Applications mapping.
- ASI01Agent goal hijackMitigates
- ASI02Tool misuseSolves
- ASI03Identity and privilege abuseSolves
- ASI04Supply chainSolves
- ASI05Unexpected code executionContains
- ASI06Memory and context poisoningMitigates
- ASI07Insecure inter-agent commsSolves
- ASI08Cascading failuresMitigates
- ASI09Human-agent trust exploitationSolves
- ASI10Rogue agentsSolves
Vulnerability disclosure
Report a vulnerability privately.
Email us, not a public issue. We aim to reply within 3 business days.
- 90-day default timeline
- Credit if you want it
- Fixes on the latest minor
In scope
- Sandbox escapes caused by MAQPNA configuration
- Token forgery, replay or scope confusion
- Attestation bypasses
- Policy, approval or rate-limit bypasses
- Undetected audit-ledger tampering
- Any unexpected outbound call
Upstream bugs (gVisor, Kata, Kubernetes) go upstream; tell us if our defaults make them worse.
Verify it yourself.
The installers check the checksum and, with cosign, the signature.
curl -fsSL https://maqpna.com/install.sh | shirm https://maqpna.com/install.ps1 | iex