VegaSec / Audit certificate

Audit completion certificate

VSS-20261003-SPW8AU52 · issued October 3, 2026 at 7:52 PM

signedvss-certificate-1coverage partial

Target and scope

Source
access-control-parity-wallet-bug-1.sol
Provenance
Submitter-provided source (paste)
Source hash (sha256)
ca6d797c809ab8f67d8833e1208a16d7f284307ed0418fdd29a171d0b6e7cec9

Analyzers

slither not recordedsemgrep 1.163.0

Findings by severity

1 critical0 high0 medium0 low0 informational1 finding2 warnings

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 coverage degraded: no installed solc satisfies pragma "0.4.9" (installed: 0.4.26, 0.5.17, 0.6.12, 0.7.6, 0.8.19, 0.8.20, 0.8.28, 0.8.30). Install a matching solc via solc-select.; 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 coverage degraded: no installed solc satisfies pragma "0.4.9" (installed: 0.4.26, 0.5.17, 0.6.12, 0.7.6, 0.8.19, 0.8.20, 0.8.28, 0.8.30). Install a matching solc via solc-select.
  • slither exit 1:

Integrity and signature

Integrity and authorship only. A valid signature proves these bytes came from VegaSec unchanged; it does not prove the audited contract is safe. Read the coverage status and the limitations above.

Canonical version
vss-canonical-1
Signature
Ed25519 · key vsig-2026-09
Report hash (sha256)
ca1c01aa64544f247bfb8a717347d29bf1c9bf9bc5c59eaa36529fd1bffd91a7
Certificate version
vss-certificate-1

Verify it without trusting this page

  1. 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-20261003-SPW8AU52
  2. 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. 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. 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-20261003-SPW8AU52"}'
  5. 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
  • This certificate is generated from the signed Solidity report artifact. It states what was scanned, with which analyzers, and what the scan found.
  • It is static-analysis triage, not a certification, a formal audit attestation or financial advice. Findings can include false positives and can miss patterns the configured detectors do not cover.
  • Verification proves the artifact's integrity and authorship. It does not prove the audited contract is safe.

https://vegasec.je4ndev.com/certificate/VSS-20261003-SPW8AU52 · https://vegasec.je4ndev.com