VegaSec / Audit certificate
Audit completion certificate
VSS-20261004-II5D1XKD · issued October 4, 2026 at 12:37 AM
Target and scope
- Source
- UniswapV2Pair.sol
- Provenance
- Etherscan verified source
- Chain
- ETHEREUM
- Contract address
- 0x0d4a11d5eeaac28ec3f61d100daf4d40471f1852
- Contract name
- UniswapV2Pair
- Compiler
- v0.5.16+commit.9c3226ce
- File count
- 1
- Source hash (sha256)
- df7d44b9887cf8aac44146e23d892c2612ad54ea70483b0de2ef1f427b1871bd
Public source: explorer record ↗
Analyzers
Findings by severity
Trust score recorded in the signed artifact: 50/100. Scores are a deterministic triage signal, not a safety guarantee.
Declared limitations
- VegaSec runs static analysis only. Findings can include false positives, miss patterns the configured detectors do not cover, and never replace manual auditor judgement.
- Scan ran slither and semgrep against a single sandboxed copy of the source. Multi-file dependency analysis beyond what slither resolves automatically is out of scope.
- Analyzer coverage is PARTIAL: at least one required analyzer (slither, semgrep) did not complete. The trust score is capped at 50/100 and the verdict can never be a clean surface. Reasons: slither produced no structured output (exit 1); slither exit 1:
- Some detectors emitted warnings (see `warnings`); their output was still ingested but should be read with extra care.
- This report is not a certification, audit attestation, or financial advice.
- slither produced no structured output (exit 1)
- slither exit 1:
Verify it without trusting this page
1. Fetch the signed bytes
This endpoint returns the exact canonical bytes that were signed, with the signature in the response headers.
curl -sS -D headers.txt -o report.json https://vegasec.je4ndev.com/api/public/report/VSS-20261004-II5D1XKD
2. Recompute the hash
The sha256 of report.json must equal the x-vegasec-report-hash header and the report hash printed on this certificate.
shasum -a 256 report.json
3. Verify the signature with the published key
The signature is Ed25519 over sha256(report.json). The public keys are published as plain JSON; verify with any Ed25519 library using the key id from the headers.
curl -sS https://vegasec.je4ndev.com/.well-known/vegasec-signing-keys.json
4. Or use the hosted verifier
POST the report id to the public verification API, or open the verify page. A response of valid:true means the served bytes carry a valid signature from a published, non-revoked key.
curl -sS -X POST https://vegasec.je4ndev.com/api/public/verify -H 'content-type: application/json' -d '{"id":"VSS-20261004-II5D1XKD"}'5. Compare the facts on this certificate with the signed bytes
severity_counts, analyzer_versions, generated_at, source_filename and limitations are fields of the signed preimage. Read them from report.json and compare with this certificate: a mismatch means the certificate does not describe the signed artifact.
cat report.json