VegaSec / Audit certificate
Audit completion certificate
VSS-20261004-S7XEDXZJ · issued October 4, 2026 at 12:36 AM
Target and scope
- Source
- Unitroller.sol
- Provenance
- Etherscan verified source
- Chain
- ETHEREUM
- Contract address
- 0x3d5bc3c8d13dcb8bf317092d84783c2697ae9258
- Contract name
- Unitroller
- Compiler
- v0.5.17+commit.d19bba13
- File count
- 12
- Source hash (sha256)
- 4463d2ca6829f3a838f3d9b3cf4d15860072dbaa1c5f1f0c4f5aa0787d6b9863
Public source: explorer record ↗
Analyzers
Findings by severity
Trust score recorded in the signed artifact: 0/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 multi-file sandboxed bundle of 12 Solidity file(s). Imports resolve between the bundled files; dependencies outside the bundle (an npm package, another repo, a generated file) are NOT analyzed, and an unresolved import makes the run partial rather than clean.
- 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.
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-S7XEDXZJ
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-S7XEDXZJ"}'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