Deterministic offline Chromium LevelDB .log carver, PNG/JPEG ICC provenance inspector, financial checksum validator & StarShield-Bench-24
starshield-forensics (v0.3.8 — Clean-Room Deterministic DFIR & MCP Toolkit)English | 简体中文 (
README.zh-CN.md)
Deterministic Chromium & Electron IndexedDB / LevelDB
.logMulti-Schema Record Carver, Structural PNG/JPEG Container Inspector, Financial Checksum Validator & Zero-DependencyMCPServerAuthor: Ziqi Xiao (
@Ziqi) · PyPI:starshield-forensics 0.3.8 (PEP 740)· Homebrew:Ziqi/tap/starshield-forensics· Concept DOI:10.5281/zenodo.24145804(v0.3.7:10.5281/zenodo.24156262) · SWHID:swh:1:snp:4ed5efec...· OpenSSF Best Practices:#16602 (SILVER — 226%)· Scorecard:8.0 / 10 (Fuzzing 10/10 · 11/18 Perfect Checks)· Provenance: SLSA L3 & Sigstore/attestations· Method Validation: UK FSR Statutory Code (FSA – DIG 100) / ISO 17025 Summary · License: MIT (REUSE 3.3) · Runtime: Python >= 3.10 (stdlib only, zero network calls, zero LLM dependencies)
starshield-forensics is an offline, read-only binary inspection and evidence triage toolkit serving three primary audiences with zero third-party dependencies:
starshield inspect-image): Millisecond structural verification of reimbursement receipts, payment screenshots, and disputed attachments—verifying RFC 2083 PNG chunk CRC32 integrity (IHDR/IDAT/IEND/iCCP), multi-segment ISO 10918 JPEG APP2 ICC_PROFILE color headers (acsp), and Photoshop APP13 (8BIM) resource blocks alongside offline ISO-7812 Luhn / 89-country ISO-13616 IBAN Mod-97 / ISO-9362 SWIFT validation.starshield precheck & parse-leveldb-log): Read-only local health check and uncompacted .log write-ahead log recovery for corrupted Chromium browser (Chrome, Edge, Brave) and Electron desktop app (VS Code, Slack, Microsoft Teams, Discord, WhatsApp Desktop) IndexedDB / Local Storage caches using strict masked Castagnoli CRC32C (0xA282EAD8) verification.UK FSR FSA – DIG 100 / ISO 17025 Aligned): Byte-offset-cited carving of soft-deleted or edited web-messaging and B2B portal records with explicit four-tier epistemic tagging (OBSERVED / DERIVED / INFERRED / UNKNOWN) and ephemeral HMAC-SHA256 pseudonymization.All bundled fixtures in samples/ and starshield/data/—plus the seeded 24-case evaluation suite in benchmark/benchmark_suite.py (StarShield-Bench-24)—are 100% clean-room specification test vectors modeled on a fictional 2025 UK supplier-invoice scenario (GBP 18,400.00, ISO-13616 example IBANs GB82WEST12345698765432 and NO9386011117947, Luhn test string 6200000000000005). Zero real incident data or PII is included.
v0.3.8)Every analytical output carries an explicit machine-readable epistemic tier so investigators and solicitors never conflate raw bytes with interpretive leads:
OBSERVED: Directly present in raw input bytes, chunk headers, or JSON fields (bound to physical WAL frame offsets or chunk offsets).DERIVED: Deterministically computed from raw input via standardized algorithms (Castagnoli CRC32C, ISO/IEC 7812 Luhn, ISO-13616 Mod-97, UTC delta arithmetic).INFERRED: Contextual triage lead requiring external corroboration (e.g., server-side bank logs or subpoenaed ISP records); never asserted as standalone proof.UNKNOWN: Explicitly outside the evidentiary boundary of local client artifacts (e.g., records compacted prior to acquisition).