TW / Independent
← Research audits

Engineering Audit / 2026-10-12

Engineering audit: local analysis tools

Bounded review of purpose, outputs and claim limits of our tools. No certification or full code audit of every release.

Scope
Roles, outputs and exports of BinDiff, Detector, PixelSteg and StaticArtifactLab.
Method
Bounded functionality and workflow review
Evidence
Project descriptions and public repositories
Finding

Distinct tasks; common input and result documentation.

Not a complete code audit of every release.

Question and scope

This engineering audit examines which claims our local tools support and where they stop. BinDiff compares files from several perspectives. Detector and PixelSteg address other static analysis questions. StaticArtifactLab documents artifacts and the examined case scope.

This is neither a full code audit of all releases nor certification of detection performance.

Tracing results

BinDiff separates structure, metadata and similarity into different views. StaticArtifactLab ties examined content to file characteristics and records skipped or rejected work in coverage.

The reader needs to know which inputs were examined. An empty result without coverage is not equivalent to a completed review.

Counterchecking claims

The linked repositories expose implementations, releases and documented limitations. They allow independent inspection of the relevant version.

Static characteristics alone prove neither malicious functionality nor harmlessness. A digest identifies bytes, not their original provenance. Similarity does not prove authorship.

Why the tools remain separate

File comparison, static characteristics and documentation of nested content answer different questions. A shared score would obscure those distinctions.

The projects are therefore assessed individually. Availability of a particular feature must be checked against the documented release of its repository. The portfolio does not replace that version check.

Implications for use

First define the analysis question, then choose the relevant tool and version. Read the export alongside inputs and coverage. Unexamined areas remain unexamined.

The tools supply observations for a professional decision. This review does not classify them as antivirus products, sandboxes or complete incident-response solutions.

Findings at a glance

  • The tools supply observations, not a universal verdict.
  • Engineering review of documented tool roles; not a complete implementation, performance or detection assessment.

Review limits

  • Engineering review of documented tool roles; not a complete implementation, performance or detection assessment.
  • This account does not extend the reviewed scope.

References

The links provide project context. The judgment rests on the evidence described in the audit. Review models and actual tool excerpts are labelled separately.

BinDiff ↗Detector ↗PixelSteg ↗StaticArtifactLab ↗
Final assessment

Conclusion

The tools supply observations, not a universal verdict.

File comparison, static characteristics and artifact documentation remain separate tasks. A useful export shows inputs, version and coverage. Without those details its meaning cannot be reliably assessed.

Next steps

  • Check the required feature against the specific release.
  • Read exports alongside inputs and coverage.
Basis of this judgmentEngineering review of documented tool roles; not a complete implementation, performance or detection assessment.
Roles, outputs and exports of BinDiff, Detector, PixelSteg and StaticArtifactLab.
← All research audits

Start a conversation

Discuss your project.

Start a conversation