Skip to content

Milestones

List view

  • v1.0.0 - Production Release

    95%+ compatibility with GNU file test corpus validated. All Core Flow specs implemented. Production-ready, memory-safe alternative to C libmagic. ## Recommended Implementation Order 1. **#48** — Establish compatibility baseline and CI tracking (NORMAL) — un-ignore tests, track pass rate 2. **#57** — Epic: Compatibility Validation & v1.0 (NORMAL) — achieve 77/81 (95%) pass rate, final docs, tag release ## Prerequisites All v0.3.0 and v0.4.0 milestones must be complete before v1.0 validation begins.

    No due date
    •1/5 issues closed
    20% complete4 open1 closed

  • v0.4.0 - API & UX Polish

    Library builder pattern, JSON metadata output, parse warnings, improved error messages, timeout partial results. Completes Core Flow spec compliance. ## Recommended Implementation Order 1. **#45** — MagicDatabase builder pattern (NORMAL) — public API improvement, best done early in the release 2. **#46** — JSON output metadata object (NORMAL) — completes JSON output spec 3. **#47** — Parser warnings for skipped rules (NORMAL) — diagnostic quality improvement 4. **#44** — Timeout returns partial results instead of error (LOW) — graceful degradation 5. **#49** — Better magic-file-not-found error message (LOW) — UX polish ## Epic - **#56** — Core Flow Spec Compliance (#44, #45, #46, #47, #49)

    No due date
    •0/4 issues closed
    0% complete4 open0 closed

  • v0.3.0 - Advanced Features

    Offset resolution, regex/search, meta-types, and compound document detection. Enables complex binary format analysis and text file detection. ## Recommended Implementation Order 1. **#37** — Indirect offset resolution (HIGH) — unblocks PE/binary format detection 2. **#38** — Relative offset resolution (HIGH) — unblocks nested rule structures 3. **#39** — Regex and search types (HIGH) — unblocks text detection (~15 test corpus cases) 4. **#42** — Meta-types: default, clear, name, use, indirect (NORMAL) — enables rule composition 5. **#51** — ZIP content inspection (LOW) — depends on #37, #39, #42 6. **#106** — Evaluate and implement fuzzing tests (MEDIUM) — best after complex parsing paths land ## Epics - **#54** — Type System Expansion (remaining: #39, #42) - **#55** — Offset Resolution (#37, #38)

    No due date
    •5/13 issues closed
    38% complete8 open5 closed